Address space layout randomization (ASLR) is a computer security technique involved in protection from buffer overflow attacks. In order to prevent an attacker from reliably jumping to a particular exploited function in memory (for example), ASLR involves randomly arranging the positions of key data areas of a program, including the base of the executable and the positions of the stack, heap, and libraries, in a process's address space.

## History

In 1997 Memco Software implemented a limited form of stack randomization as part of its SeOS Access Control product.[1]

The PaX project first coined the term "ASLR". It published the first design and implementation of ASLR in July 2001. This remains the most complete implementation, providing also kernel stack randomization from October 2002 onward. It also continues to provide the most entropy for each randomized layout compared to other implementations.[2]

## Benefits

Address space randomization hinders some types of security attacks by making it more difficult for an attacker to predict target addresses. For example, attackers trying to execute return-to-libc attacks must locate the code to be executed, while other attackers trying to execute shellcode injected on the stack have to find the stack first. In both cases, the system obscures related memory-addresses from the attackers. These values have to be guessed, and a mistaken guess is not usually recoverable due to the application crashing.

### Effectiveness

Address space layout randomization is based upon the low chance of an attacker guessing the locations of randomly placed areas. Security is increased by increasing the search space. Thus, address space randomization is more effective when more entropy is present in the random offsets. Entropy is increased by either raising the amount of virtual memory area space over which the randomization occurs or reducing the period over which the randomization occurs. The period is typically implemented as small as possible, so most systems must increase VMA space randomization.

To defeat the randomization, attackers must successfully guess the positions of all areas they wish to attack. For data areas such as stack and heap, where custom code or useful data can be loaded, more than one state can be attacked by using NOP slides for code or repeated copies of data. This allows an attack to succeed if the area is randomized to one of a handful of values. In contrast, code areas such as library base and main executable need to be discovered exactly. Often these areas are mixed, for example stack frames are injected onto the stack and a library is returned into.

To begin, let us declare the following variables:

$E_s$ = entropy bits of stack top
$E_m$ = entropy bits of mmap() base
$E_x$ = entropy bits of main executable base
$E_h$ = entropy bits of heap base
$A_s$ = attacked bits per attempt of stack entropy
$A_m$ = attacked bits per attempt of mmap() base entropy
$A_x$ = attacked bits per attempt of main executable entropy
$A_h$ = attacked bits per attempt of heap base entropy
$\alpha$ = attempts made

Where $N$ is the total amount of entropy:

$N = E_s-A_s + E_m-A_m + E_x-A_x + E_h-A_h\,$

To calculate the probability of an attacker succeeding, we have to assume a number of attempts $\alpha$ carried out without being interrupted by a signature-based IPS, law enforcement, or other factor; in the case of brute forcing, the daemon cannot be restarted. We also have to figure out how many bits are relevant and how many are being attacked in each attempt, leaving however many bits the attacker has to defeat.

The following formulas represent the probability of success for a given set of $\alpha\,$ attempts on $N$ bits of entropy.

$g \left ( \alpha\, \right ) = \mbox{isolated guessing; address space is re-randomized after each attempt}\,$
$g \left ( \alpha\, \right ) = 1 - { \left ( 1 - {2^{-N}} \right ) ^ \alpha\,} : 0 \le \, \alpha\,$
$b \left ( \alpha\, \right ) = \mbox{systematic brute forcing on copies of the program with the same address space}$
$b \left ( \alpha\, \right ) = \frac{\alpha\,}{{2^N}} : 0 \le \, \alpha\, \le \, {2^N}$

In many systems, $2^N$ can be in the thousands or millions; on modern 64-bit systems, these numbers typically reach the millions at least. For 32-bit systems at 2004 computer speeds which have 16 bits for address randomization, Shacham and co-workers state "… 16 bits of address randomization can be defeated by a brute force attack within minutes."[3] It should be noted that the authors' statement depends on the ability to attack the same application multiple times without any delay. Proper implementations of ASLR, like that included in grsecurity, provide several methods to make such brute force attacks infeasible. One method involves preventing an executable from executing for a configurable amount of time if it has crashed a certain number of times.

Some systems implement Library Load Order Randomization, a form of ASLR which randomizes the order in which libraries are loaded. This supplies very little entropy. An approximation of the number of bits of entropy supplied per needed library appears below; this does not yet account for varied library sizes, so the actual entropy gained is really somewhat higher. Note that attackers usually need only one library; the math is more complex with multiple libraries, and shown below as well. Note that the case of an attacker using only one library is a simplification of the more complex formula for $l = 1$.

$l$ = number of libraries loaded
$\beta\,$ = number of libraries used by the attacker
$E_m = \log_2 \left (l \right ) : \beta\, = 1, l \ge \, 1$
$E_m = \sum_{i=l}^{l - \left ( \beta\, - 1 \right )} \log_2 \left (i \right ) : \beta\, \ge \, 1, l \ge \, 1$

These values tend to be low even for large values of $l$, most importantly since attackers typically can use only the C standard library and thus one can often assume that $\beta\, = 1$. Interestingly, however, even for a small number of libraries there are a few bits of entropy gained here; it is thus potentially interesting to combine library load order randomization with VMA address randomization to gain a few extra bits of entropy. Note that these extra bits of entropy will not apply to other mmap() segments, only libraries.

#### Reducing entropy

Attackers may make use of several methods to reduce the entropy present in a randomized address space, ranging from simple information leaks to attacking multiple bits of entropy per attack (such as by heap spraying). There is little that can be done about this.

It is possible to leak information about memory layout using format string vulnerabilities. Format string functions such as printf use a variable argument list to do their job; format specifiers describe what the argument list looks like. Because of the way arguments are typically passed, each format specifier moves closer to the top of the stack frame. Eventually, the return pointer and stack frame pointer can be extracted, revealing the address of a vulnerable library and the address of a known stack frame; this can completely eliminate library and stack randomization as an obstacle to an attacker.

One can also decrease entropy in the stack or heap. The stack typically must be aligned to 16 bytes, and so this is the smallest possible randomization interval; while the heap must be page-aligned, typically 4096 bytes. When attempting an attack, it is possible to align duplicate attacks with these intervals; a NOP slide may be used with shellcode injection, and the string '/bin/sh' can be replaced with '////////bin/sh' for an arbitrary number of slashes when attempting to return to system. The number of bits removed is exactly $\log_2\!\left (n \right )$ for $n$ intervals attacked.

Such decreases are limited due to the amount of data in the stack or heap. The stack, for example, is typically limited to 8 MB[4] and grows to much less; this allows for at most 19 bits, although a more conservative estimate would be around 8–10 bits corresponding to 4–16 KB[4] of stack stuffing. The heap on the other hand is limited by the behavior of the memory allocator; in the case of glibc, allocations above 128 KB are created using mmap, limiting attackers to 5 bits of reduction. This is also a limiting factor when brute forcing; although the number of attacks to perform can be reduced, the size of the attacks is increased enough that the behavior could in some circumstances become apparent to intrusion detection systems.

## Implementations

Several mainstream, general-purpose operating systems implement ASLR.

### FreeBSD

FreeBSD does not support ASLR as of January 2014. However, Oliver Pinter started work on a basic ASLR patch and Shawn Webb picked up the patch and started enhancing it under the direction of SoldierX. Active work on ASLR is being done on Shawn Webb's ASLR branch on GitHub.

### OpenBSD

Two years after ASLR was invented and published as part of PaX, a popular security patch for Linux, OpenBSD became the first mainstream operating system to support partial ASLR (and to activate it by default).[5] OpenBSD completed its ASLR support after Linux in 2008 when it added support for PIE binaries.[6] More about Exploit Mitigation Techniques: an Update After 10 Years in OpenBSD.

### DragonFly BSD

DragonFly BSD has an implementation of ASLR based upon OpenBSD's model, added in 2010.[7] It is off by default, and can be enabled by setting the sysctl vm.randomize_mmap to 1.

### Linux

Linux has enabled a weak form of ASLR by default since kernel version 2.6.12 (released June 2005).[8] The PaX and Exec Shield patchsets to the Linux kernel provide more complete implementations. Various Linux distributions including Adamantix, Alpine Linux, Hardened Gentoo, and Hardened Linux From Scratch come with PaX's implementation of ASLR by default.

The Exec Shield patch for Linux supplies 19 bits of stack entropy on a period of 16 bytes; and 8 bits of mmap base randomization on a period of 1 page of 4096 bytes. This places the stack base in an area 8 MB wide containing 524 288 possible positions; and the mmap base in an area 1 MB wide containing 256 possible positions.

Position-independent executable (PIE) implements a random base address for the main executable binary and has been in place since 2003. It provides the same address randomness to the main executable as being used for the shared libraries. The PIE feature is in use only for the network facing daemons – the PIE feature cannot be used together with the prelink feature for the same executable.

The prelink tool implements randomization at prelink time rather than runtime, because by design prelink aims to handle relocating libraries before the dynamic linker has to, which allows the relocation to occur once for many runs of the program. As a result, real address space randomization would defeat the purpose of prelinking.

Support for address space randomization for the Linux kernel itself, which randomizes where the kernel code is placed at boot time,[9] was merged into the Linux kernel mainline in kernel version 3.14, released on 30 March 2014.[10] When compiled in, it can be disabled at boot time by specifying nokaslr as one of the kernel's boot parameters.[11]

### Android

Android 4.0 Ice Cream Sandwich provides address space layout randomization (ASLR) to help protect system and third party applications from exploits due to memory-management issues. Position-independent executable support was added in Android 4.1.[12]

### Solaris

ASLR has been introduced in Solaris beginning with Solaris 11.1. ASLR in Solaris 11.1 can be set either by way of Zones or on a binary basis.[13]

### Microsoft Windows

Microsoft's Windows Vista (released January 2007) and later have ASLR enabled for only those executables and dynamic link libraries specifically linked to be ASLR-enabled.[14] For compatibility, it is not enabled by default for other applications. Typically, only older software is incompatible and ASLR can be fully enabled by editing a registry entry "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\MoveImages".,[15] or by installing Microsoft's Enhanced Mitigation Experience Toolkit.

The locations of the heap, stack, Process Environment Block, and Thread Environment Block are also randomized. A security whitepaper from Symantec noted that ASLR in 32-bit Windows Vista may not be as robust as expected, and Microsoft has acknowledged a weakness in its implementation.[16]

Host-based intrusion prevention systems such as WehnTrust[17] and Ozone[18] also offer ASLR for Windows XP and Windows Server 2003 operating systems. WehnTrust is open-source.[19] Complete details of Ozone's implementation is not available.[20]

It was noted in February 2012[21] that ASLR on 32-bit Windows systems prior to Windows 8 can have its effectiveness reduced in low memory situations. Similar effect also had been achieved on Linux in the same research. The test code caused the Mac OS X 10.7.3 system to kernel panic, so it was left unclear about its ASLR behavior in this scenario.

### OS X

In Mac OS X Leopard 10.5 (released October 2007), Apple introduced randomization for system libraries.[22]

In Mac OS X Lion 10.7 (released July 2011), Apple expanded their implementation to cover all applications, stating "address space layout randomization (ASLR) has been improved for all applications. It is now available for 32-bit apps (as are heap memory protections), making 64-bit and 32-bit applications more resistant to attack."[23]

As of OS X Mountain Lion 10.8 (released July 2012) and later, the entire system including the kernel as well as kexts and zones are randomly relocated during system boot.[24]

### iOS (iPhone, iPod touch, iPad)

Apple introduced ASLR in iOS 4.3 (released March 2011).[25]

## References

1. ^ US patent 5949973, Yarom, Yuval, "Method of relocating the stack in a computer system for preventing overrate by an exploit program", issued 1999-09-07, assigned to Memco Software, Ltd.
2. ^ Comparison of PaX to Exec Shield and W^X
3. ^ On the Effectiveness of Address-Space Randomization, Shacham, H. and Page, M. and Pfaff, B. and Goh, E.J. and Modadugu, N. and Boneh, D, Proceedings of the 11th ACM conference on Computer and communications security, pp 298—307, 2004
4. ^ a b Transistorized memory, such as RAM, ROM, flash and cache sizes as well as file sizes are specified using binary meanings for K (10241), M (10242), G (10243), ...
5. ^ Theo De Raadt (2005). "Exploit Mitigation Techniques (updated to include random malloc and mmap) at OpenCON 2005". Retrieved 26 August 2009.
6. ^ Kurt Miller (2008). "OpenBSD's Position Independent Executable (PIE) Implementation". Archived from the original on 12 June 2011. Retrieved 22 July 2011.
7. ^ mmap - add mmap offset randomization, DragonFly Gitweb, 25 November 2010.
8. ^ The NX Bit And ASLR, Tom's Hardware, 25 March 2009.
9. ^ Jake Edge (2013-10-09). "Kernel address space layout randomization". LWN.net. Retrieved 2014-04-02.
10. ^ "1.7. Kernel address space randomization". Linux kernel 3.14. kernelnewbies.org. 2014-03-30. Retrieved 2014-04-02.
11. ^ "kernel/git/torvalds/linux.git: x86, kaslr: Return location from decompress_kernel". Linux kernel source tree. kernel.org. 2013-10-13. Retrieved 2014-04-02.
12. ^ "Android Security". Android Developers. Retrieved 7 July 2012.
13. ^ Controlling Access to Machine Resources, Oracle Information Library, 26 October 2012.
14. ^ "Windows ISV Software Security Defenses". Msdn.microsoft.com. Retrieved 10 April 2012.
15. ^ Windows Internals: Including Windows Server 2008 and Windows Vista, Fifth Edition (PRO-Developer) ISBN 978-0-7356-2530-3
16. ^ Ollie Whitehouse (February 2007). "An Analysis of Address Space Layout Randomization on Windows Vista" (PDF).
17. ^ "WehnTrust". Codeplex.com. Retrieved 10 April 2012.
18. ^ "Security Architects' Ozone". Securityarchitects.com. Retrieved 10 April 2012.
19. ^ "WehnTrust source code". Retrieved 15 November 2013.
20. ^ "Address-Space Randomization for Windows Systems" (PDF). Retrieved 10 April 2012.
21. ^ Posted by Ollie (2 March 2012). "Research, Develop, Assess, Consult & Educate | Recx: A Partial Technique Against ASLR – Multiple O/Ss". Recxltd.blogspot.co.uk. Retrieved 10 April 2012.
22. ^ "Mac OS X – Security – Keeps safe from viruses and malware". Apple. Retrieved 10 April 2012.
23. ^ "Security". Apple Inc. Archived from the original on 6 June 2011. Retrieved 6 June 2011.
24. ^ "OS X Mountain Lion Core Technologies Overview". June 2012. Retrieved 25 July 2012.
25. ^