• Severity Rating • Fix Information • Vulnerable Software Versions • SCAP Mappings
The safe mode checks in PHP 4.x to 4.3.9 and PHP 5.x to 5.0.2 truncate the file path before passing the data to the realpath function, which could allow attackers to bypass safe mode. NOTE: this issue was originally REJECTed by its CNA before publication, but that decision is in active dispute. This candidate may change significantly in the future as a result of further discussion.
Note: References are provided for the convenience of the reader to help distinguish between vulnerabilities. The list is not intended to be complete.
Date Entry Created
20041123 Disclaimer: The entry creation date may reflect when the CVE-ID was allocated or reserved, and does not necessarily indicate when this vulnerability was discovered, shared with the affected vendor, publicly disclosed, or updated in CVE.
Phase (Legacy)
Assigned (20041123)
Votes (Legacy)
REVIEWING(1) Christey
Comments (Legacy)
 Christey> There is active disagreement regarding whether this satisfies the
   criteria for inclusion in CVE, because the attack vectors require
   function parameters that are typically controlled only by the
   application developer, not an external attacker.  This would mean that
   only the PHP application owner could exploit it.
   Since various PHP functions already allow the application owner to
   execute commands, no additional privileges would be gained by
   exploiting such a bug.  However, if safe_mode is enabled in PHP, then
   the PHP functions related to execution are restricted
   (e.g. shell_exec()).  Thus, exploitation may allow the PHP application
   owner to execute code *despite* the configured restrictions imposed by
   safe mode, which then qualifies this as a vulnerability.

Proposed (Legacy)
This is an entry on the CVE list, which standardizes names for security problems.