NX bit
NX stands for "no execute", a technology used in CPUs such as Sun's Sparc, Transmeta's Efficeon, and newer 64-bit x86 processors to prevent code from being executed on areas of memory flagged with an NX bit. This feature signifigantly lowers the probability of hackers exploiting buffer overflows and increases overall system security.
An operating system with the ability to emulate and/or take advantage of an NX bit may prevent the stack and heap from being executable, and may prevent executable memory from being writable. 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, to be both writable and executable; if it is not, the attack fails.
This technology is implemented in different ways by different operating systems. As of June 2004, Redhat kernel developer Ingo_Molnar released a Linux kernel patch named Exec-shield to fully utilize the NX bit in supporting CPUs from Intel, AMD, Transmeta and VIA. For CPUs that do not support a hardware NX bit, such as the 32-bit x86 processor family, a kernel patch named PaX can emulate NX functionality. However, the Linux kernel does not ship with PaX, which must be installed manually. Microsoft plans to support NX capabilities in Windows XP Service pack 2 and Longhorn. Finally, the OpenBSD project supports software NX through W^X, which also supports hardware NX on Alpha, AMD64, HPPA, and Sparc processors.
External links
- CPU-Based Security: The NX Bit
- OpenBSD 3.3 Release
- Exec-Shield Homepage
- PaX Homepage
- Transmeta To Add 'NX' Antivirus Feature To Chips
- AMD, Intel put antivirus tech into chips
- Microsoft Interviewed on Trustworthy Computing and NX