Buffer overflow: Difference between revisions
Jump to navigation
Jump to search
imported>Eric M Gearhart (Category add) |
imported>Eric M Gearhart (Added Smashing the Stack and references section) |
||
| Line 3: | Line 3: | ||
This error is the most common type of [[Computer security]] flaw that is used to run code on a remote machine unintentionally. | This error is the most common type of [[Computer security]] flaw that is used to run code on a remote machine unintentionally. | ||
Other names for this attack include "buffer overrun" and "Smashing the Stack," both of which describe the concept. | Other names for this attack include "buffer overrun" and "Smashing the Stack," both of which describe the concept.<ref name="Smashing the Stack">{{cite web | ||
| url=http://insecure.org/stf/smashstack.html | |||
| title="Smashing the Stack for Fun and Profit by Aleph One" | |||
| retrievedate=2007-04-09 | |||
}}</ref> | |||
==References== | |||
<references/> | |||
[[Category:CZ Live]] | [[Category:CZ Live]] | ||
[[Category:Computers Workgroup]] | [[Category:Computers Workgroup]] | ||
Revision as of 11:58, 9 April 2007
In computers and computer security, a buffer overflow occurs when more data than was expected is written to a memory buffer than was intended by a programmer.
This error is the most common type of Computer security flaw that is used to run code on a remote machine unintentionally.
Other names for this attack include "buffer overrun" and "Smashing the Stack," both of which describe the concept.[1]