SecurityReason.com - Our Reason is

Security

Register | Forget Password | Login
Search :
SecurityReason
IT News
Search
SecurityAlert Database
About SecurityAlert
ExploitAlert Database
SecurityReason Research
WLB
WLB Database
Send to WLB
About WLB
Services
Security Audit
Schedule
Prices of services
Contact
RSS
SecurityReason IT News
SecurityAlert
World Laboratory of Bugtraq
ExploitAlert
Apache
PHP
Corporate
Contact
About SecurityReason
Note

If you have found a vulnerability, please send to our SecurityAlert Database :
secalert()securityreason()com

Also if you have new ( 0-day ) exploit, please send to our ExploitAlert Archive :
exploit()securityreason()com
Home arrow SecurityAlert Database

Arrow  Topic :

PHP session.save_path open_basedir Bypass Vulnerability


Arrow  SecurityAlert : 2507
Arrow  CVE : GENERIC-MAP-NOMATCH
Arrow  SecurityRisk : Medium  Security Risk Medium  (About)
Arrow  Remote Exploit : No
Arrow  Local Exploit : Yes
Arrow  Exploit Given : Yes
Arrow  Credit : Stefan Esser
Arrow  Published : 01.04.2007

Arrow  Affected Software : Affected are PHP 4 < 4.4.5 and PHP 5 < 5.2.1



Arrow  Advisory Text :  

When an empty session save path is supplied the files session storage
modules falls back to the path specified by the TMPDIR environment
variable. Unfortunately this magic fallback happens after the open_basedir
check and can therefore be used to bypass it.

Detailed information

The summary and the POC say it all.
Proof of concept, exploit or instructions to reproduce

To check this problem try the following code, when open_basedir is set.

<?php
ini_set("session.save_path", "/sessions/user2/");
putenv("TMPDIR=/sessions/user2/");
ini_set("session.save_path", "");
@session_start();
?>

The first ini_set() will error out, because the path is in violation with
the open_basedir. The second ini_set() will succeed and the session file
will be created in the path specified by TMPDIR.
Notes

We recommend to never ever rely on open_basedir. We consider the
open_basedir restrictions just a nice way to decrease the impact of include
vulnerabilities.

The MOPB should have made clear by now, that the moment an attacker is able
to run PHP code, PHP has more than enough flaws for him to bypass all
restrictions enforced by the PHP interpreter.




Arrow  Feedback :

If you have additional information or notice any errors regarding this security advisory, please use contact form or email us at info()securityreason()com.
Alert

Multiple Vendors libc/gdtoa printf(3) Array Overrun

Security Risk High- 2009-05-30

SecurityReason realised new advisory about vulnerabilities libc/gdtoa...
Apache RSS Apache Alert

» Apache Tomcat
   RequestDispatcher
   directory traversal
   vulnerability

» Apache mod_dav / svn
   Remote Denial of Service
   Exploit

» Apache Tomcat Information
   disclosure

» Apache Tomcat User
   enumeration vulnerability
   with FORM authentication
PHP RSS PHP Alert

» PHP 5.2.9 curl safe_mode
   & open_basedir bypass

» PHP 5.2.6 SAPI
   php_getuid() overload

» PHP
   ZipArchive::extractTo()
   Directory Traversal
   Vulnerability

» PHP 5.2.6 dba_replace()
   destroying file
Copyright © SecurityReason.com. All Rights Reserved.