Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 4 Dec 2014 15:47:34 -0800
From: Kees Cook <>
Cc: Hector Marco <>
Subject: Re: Offset2lib: bypassing full ASLR on 64bit Linux

On Thu, Dec 04, 2014 at 09:19:04PM +0100, Hector Marco wrote:
> This is a disclosure of a weakness of the ASLR Linux implementation.
> The problem appears when the executable is PIE compiled and it has an
> address leak belonging to the executable. We named this weakness:
> offset2lib.
> In this scenario, an attacker is able to de-randomize all mmapped
> areas (libraries, mapped files, etc.) by knowing only an address
> belonging to the application and the offset2lib value.
> We have built a PoC which bypasses on a 64 bit Linux system, the three
> most widely adopted and effective protection techniques: No-eXecutable
> bit (NX), address space layout randomization (ASLR) and stack smashing
> protector (SSP). The exploit obtains a remote shell in less than one
> second.
> We have proposed the ASLRv3 which is a small Linux patch which removes
> the offset2lib weakness.
> Details of the weakness, steps to exploit the offset2lib weakness, a working
> proof of concept exploit, recommendations and a demonstrative video
> has been
> publish at:

Thanks for the research! Following the submission guidelines[1], please
send your ASLRv3 patch to upstream at and
CC the following people:

	Andrew Morton <>
	Thomas Gleixner <>
	Ingo Molnar <>
	"H. Peter Anvin" <>
	Russell King <>
	Catalin Marinas <>
	Will Deacon <>
	Oleg Nesterov <>
	Andy Lutomirski <>
	Kees Cook <>

I noticed in testing that this hugely reduces the available mmap space
available to 32-bit processes. I suspect this is what this wasn't done




Kees Cook
Chrome OS Security

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.