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:
“Mere human beings can’t afford to be fanatical about anything.... Not even about justice or loyalty. The fanatic for justice ends by murdering a million helpless people to clear a space for his law-courts. If we are to survive on this planet, there must be compromises.”
—Storm Jameson (1891–1986)
“The best protection parents can have against the nightmare of a daycare arrangement where someone might hurt their child is to choose a place that encourages parents to drop in at any time and that facilitates communication among parents using the program. If parents are free to drop in and if they exercise this right, it is not likely that adults in that place are behaving in ways that harm children.”
—Gwen Morgan (20th century)