Linux Disable or Enable ExecShield Buffer Overflows Protection

by on April 9, 2007 · 3 comments· LAST UPDATED March 16, 2009

in , ,

Now that I have Cent OS (RHEL clone) installed on my IBM server, I'm wondering what is ExecShield and how do I disable the same?

ExecShield is security Linux kernel patch to avoid worms and other problems.

Wikipedia has more information about Exec Shield project:

Exec Shield is a project that got started at Red Hat, Inc in late 2002 with the aim of reducing the risk of worm or other automated remote attacks on Linux systems. The first result of the project was a security patch for the Linux kernel that adds an NX bit to x86 CPUs. While the Exec Shield project has had many other components, some people refer to this first patch as Exec Shield.

Task: Disable ExecShield protection

Type the following command as root user:
# sysctl -w kernel.exec-shield=0

You can disable it permanently system-wide after each and every reboot by adding following line to /etc/sysctl.conf file:
# vi /etc/sysctl.conf
Append following line
kernel.exec-shield=0

Save and close the file. Please note that I don’t recommend disabling ExecShild protection.

You can also disable protection by appending the following parameter to the kernel command line in the GRUB bootloader to kernel line:
# vi /etc/grub.conf
Modify / append exec-shield=0 parameter as follows:
kernel /vmlinuz-2.6.8 ro root=LABEL=/ exec-shield=0
Close and save the file.

Enable ExecShield Protection Against Buffer Overflows

Open your /etc/sysctl.conf file:
# vi /etc/sysctl.conf
Add the following lines:

 
kernel.exec-shield = 1
kernel.randomize_va_space = 1
 

Save and close the file. First line will enable ExecShield protection and second line will enable random placement of virtual memory regions protection. To load in sysctl settings, enter:
# sysctl -p

TwitterFacebookGoogle+PDF versionFound an error/typo on this page? Help us!

{ 3 comments… read them below or add one }

1 Miker March 17, 2009 at 12:45 pm

Does selinux supersede this now?

Reply

2 Daniel Kühl Lima November 24, 2009 at 12:08 pm

One thing is one thing, another thing is another thing.

Reply

3 Quentin M. April 5, 2011 at 2:24 pm

To be on the safe side, better use this:
kernel.exec-shield = 2
kernel.randomize_va_space = 2

The rationale behind this:
– a value of 0 completely disables ExecShield and Address Space Layout Randomization
– a value of 1 enables them ONLY if the application bits for these protections are set to “enable”
– a value of 2 enables them by default, except if the application bits are set to “disable”
– a value of 3 enables them always, whatever the application bits
– a value of

Reply

Leave a Comment

Tagged as: , , , , , , , , , , , , ,

Previous Faq:

Next Faq: