lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 8 Aug 2013 13:33:43 +0430
From: E R <>
To: king cope <>
Subject: Re: Apache suEXEC privilege elevation /
	information disclosure

hi KingCope
the one of security features in hosting servers is : dont allow to
.htaccess override from users
for doing this features in httpd.conf you can use *AllowOverride None* instead
of *AllowOverride all*
​with this feature you can not use this bug.

On Wed, Aug 7, 2013 at 8:38 PM, king cope <> wrote:

> hi...
> I posted the advisory to make administratos aware that it will be
> still possible to read files with the apache uid even when suEXEC is
> in place.
> suEXEC is installed on many hosting providers. I read the cpanel site
> describing the patches [1], tough standart apache httpd does not have
> these patches installed.
> SymLinksIfOwnerMatch will not help in this attack scenario because the
> .htaccess file overwrites this Options directive.
> If a hacker sees an apache installation using suEXEC from an attackers
> perspective it does not matter where the bug resides, either in Apache
> or in suEXEC.  He just wants to circumvent the suEXEC protection so he
> can go the way described in the text I posted. This will aid him to
> escalate privileges further.

Content of type "text/html" skipped

Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia -

Powered by blists - more mailing lists