Skip to contentSkip to conversation

how to determine if the noexec stack is defined by an application

DISCUSSION Florin Andrei 3 participants 8 messages Jun 29, 2007 – Jun 30, 2007

lore
Share & tools
lore
#0 lore raw

I'm reading Ingo's NX quick start document:

http://people.redhat.com/mingo/nx-patches/QuickStart-NX.txt

Quote:
"If an application defines a noexec stack then the kernel will enforce this executability, and all attempts to execute on the stack will be prevented by the hardware."

My question is related to the conditional "if an application". So it looks like it depends on the app. Now, the OS/hardware combination that I'm using (RHEL4 WS 32 bit on AMD64 CPU - long story, don't ask) definitely enables NX:

# grep -i nx /var/log/dmesg
NX (Execute Disable) protection: active

But it's running a Web service which is a combination of C code and Tomcat/Java. I have no clue how to determine which portions specify a noexec stack and which don't.

In case it turns out some portions do not specify a noexec stack, my next question is how to get the application to create a noexec stack (assume I can make that request to the developers).

(please do NOT Cc me, I'm subscribed to the list)

Signature · 3 lines
Florin Andrei

http://florin.myip.org/
#1 lore raw
Quoted 8 lines

But it's running a Web service which is a combination of C code and Tomcat/Java. I have no clue how to determine which portions specify a noexec stack and which don't.

In case it turns out some portions do not specify a noexec stack, my next question is how to get the application to create a noexec stack (assume I can make that request to the developers).

like this:

$ eu-readelf -l /bin/true  | grep STACK
  GNU_STACK      0x000000 0x00000000 0x00000000 0x000000 0x000000 RW 0x4

(replace /bin/true with the binary or library you want to check)

if it says "RW" like here, it'll have non-executable stack. If it says "RWX" or if this line is absent entirely, the stack will be executable.

#2 lore raw
Quoted 10 lines · Arjan van de Ven

like this:

$ eu-readelf -l /bin/true  | grep STACK
  GNU_STACK      0x000000 0x00000000 0x00000000 0x000000 0x000000 RW 0x4

(replace /bin/true with the binary or library you want to check)

if it says "RW" like here, it'll have non-executable stack. If it says "RWX" or if this line is absent entirely, the stack will be executable.

The last part is not true. Some architectures (especially newer ones) default to non-exec stack. The absense of a GNU_STACK header represents the default.

Andreas.

Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
#3 lore raw
Quoted 8 lines · Andreas Schwab
Quoted 6 lines · Arjan van de Ven

like this:

$ eu-readelf -l /bin/true  | grep STACK
  GNU_STACK      0x000000 0x00000000 0x00000000 0x000000 0x000000 RW 0x4
Quoted 8 lines
Quoted 4 lines

(replace /bin/true with the binary or library you want to check)

if it says "RW" like here, it'll have non-executable stack. If it says "RWX" or if this line is absent entirely, the stack will be executable.

The last part is not true. Some architectures (especially newer ones) default to non-exec stack. The absense of a GNU_STACK header represents the default.

ok you're right; powerpc64 defaults to non-executable stack (all others default to executable stack)

Signature · 2 lines
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
#4 lore raw
Quoted 1 line · Arjan van de Ven

(all others default to executable stack)

Except ia64.

Andreas.

Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
#5 lore raw
Quoted 5 lines · Andreas Schwab
Quoted 1 line · Arjan van de Ven

(all others default to executable stack)

Except ia64.

for ia64 it depends on the personality actually .. just to make it more complex.

Signature · 2 lines
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
#6 lore raw
In reply to Arjan van de Ven
Quoted 6 lines · Arjan van de Ven
Quoted 1 line

But it's running a Web service which is a combination of C code and Tomcat/Java. I have no clue how to determine which portions specify a noexec stack and which don't.

like this:

$ eu-readelf -l /bin/true  | grep STACK
  GNU_STACK      0x000000 0x00000000 0x00000000 0x000000 0x000000 RW 0x4

Is Sun Java 1.5 a known exception - as an application that doesn't set a noexec stack and reverts to default?

# eu-readelf -l ./java | grep STACK | wc -l
0

But then, this bug report seems to indicate otherwise, if I'm reading it correctly:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5051381

Signature · 3 lines
Florin Andrei

http://florin.myip.org/
#7 lore raw
Quoted 13 lines · Florin Andrei
Quoted 8 lines · Arjan van de Ven
Quoted 3 lines

But it's running a Web service which is a combination of C code and Tomcat/Java. I have no clue how to determine which portions specify a noexec stack and which don't.

like this:

$ eu-readelf -l /bin/true  | grep STACK
  GNU_STACK      0x000000 0x00000000 0x00000000 0x000000 0x000000 RW 0x4

Is Sun Java 1.5 a known exception - as an application that doesn't set a noexec stack and reverts to default?

Quoted 7 lines
# eu-readelf -l ./java | grep STACK | wc -l
0

But then, this bug report seems to indicate otherwise, if I'm reading it correctly:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5051381

that's not a mainline kernel; and I don't rule out that early RHEL3 versions had a 64/32 bug in this area

Quoted 1 line
Signature · 2 lines
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org