Linked by Thom Holwerda on Mon 18th Jan 2010 22:00 UTC
Thread beginning with comment 404856
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2006-01-01
the reference to a random location of freed memory could result in execution of the attacker's code.
How can this possibly work? Seriously, if a reference to a deleted object does magic such as this, that is really bad as the object has been deleted, the memory is free and anything can now be stored in the same location once it's been freed. Perhaps if the address stored in the pointer is not cleared, in other words the pointer is not set to NULL, the memory location referenced by the pointer gets filled with something else - the malicious code from outside. May be they have forgotten to NULL the pointer!
Again, I am just trying to make logic out of this!
Edited 2010-01-19 08:01 UTC