In computer security, executable space protection is the marking of memory regions as non-executable, such that an attempt to execute machine code in these regions will cause an exception. It makes use of hardware features such as the NX bit.
The Burroughs 5000 offered hardware support for executable space protection when it was introduced in 1961; that capability was retained in its successors at least through 2006. In its implementation of tagged architecture, each word of memory had an associated, hidden tag bit designating it code or data. Thus, user programs cannot write or even read a program word, and data words cannot be executed.
If an operating system can mark some or all writable regions of memory as non-executable, it may be able to prevent the stack and heap memory areas from being executable. This helps to prevent certain buffer overflow exploits from succeeding, particularly those that inject and execute code, such as the Sasser and Blaster worms. These attacks rely on some part of memory, usually the stack, being both writable and executable; if it is not, the attack fails.
Read more about Executable Space Protection: OS Implementations
Famous quotes containing the words space and/or protection:
“When Paul Bunyan’s loggers roofed an Oregon bunkhouse with shakes, fog was so thick that they shingled forty feet into space before discovering they had passed the last rafter.”
—State of Oregon, U.S. public relief program (1935-1943)
“The protection of a ten-year-old girl from her father’s advances is a necessary condition of social order, but the protection of the father from temptation is a necessary condition of his continued social adjustment. The protections that are built up in the child against desire for the parent become the essential counterpart to the attitudes in the parent that protect the child.”
—Margaret Mead (1901–1978)