4 ms·
By "read buffer" I assume they mean reading data from the AVI stream into a buffer (ie. writing to and beyond the buffer memory). Buffer overflow can corrupt a
by rwmj 7y ago
By "read buffer" I assume they mean reading data from the AVI stream into a buffer (ie. writing to and beyond the buffer memory). Buffer overflow can corrupt adjacent return addresses on the stack since those are usually in higher memory, therefore above the buffer, therefore overwritable if you can write beyond the end of the buffer. This is the "classic" stack smashing exploit, somewhat mitigated these days if your code was compiled with hardening. Or if the buffer is on the heap then any adjacent data structures which might contain pointers, especially function pointers, can be overwritten. Or inter-allocation malloc structures can be corrupted, see next point.
Double free just generally corrupts the malloc structures and all bets are off afterwards. Modern libcs usually have mitigations so they can detect certain double frees and will deliberately abort the program, but this depends on your distro having enabled hardening flags when compiling VLC (which most distros do these days).