|
PHP Multiple Vulnerabilities
|
|
Secunia Advisory:
|
SA13481
|
|
|
Release Date:
|
2004-12-16
|
|
Last Update:
|
2005-03-21
|
|
Popularity:
|
49,185 views
|
|
|
Critical:
|
Highly critical
|
|
Impact:
|
Security Bypass
Exposure of sensitive information
Privilege escalation
System access
|
|
Where:
|
From remote
|
|
Solution Status:
|
Vendor Patch
|
|
| Software: | PHP 4.3.x
PHP 5.0.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
Multiple vulnerabilities have been reported in PHP, which can be exploited to gain escalated privileges, bypass certain security restrictions, gain knowledge of sensitive information, or compromise a vulnerable system.
1) An integer overflow in the "pack()" function can be exploited to cause a heap-based buffer overflow by passing some specially crafted parameters to the function.
Successful exploitation bypasses the safe_mode feature and allows execution of arbitrary code with the privileges of the web server.
2) An integer overflow in the "unpack()" function can be exploited to leak information stored on the heap by passing specially crafted parameters to the function.
In combination with the first vulnerability, this may also allow bypassing of heap canary protection mechanisms.
3) An error within safe_mode when executing commands can be exploited to bypass the safe_mode_exec_dir restriction by injecting shell commands into the current directory name.
Successful exploitation requires that PHP runs on a multi-threaded Unix web server.
4) An error in safe_mode combined with certain implementations of "realpath()" can be exploited to bypass safe_mode via a specially crafted file path.
5) An error within the handling of file paths may potentially lead to file inclusion vulnerabilities. The problem is that "realpath()", which in some implementations truncate filenames, is used in various places to obtain the real path of a file.
6) Various errors within the deserialization code can be exploited to disclose information or execute arbitrary code via specially crafted strings passed to the "unserialize()" function.
7) A signedness error in the "shmop_write()" function can be exploited to write data to arbitrary memory locations by passing an overly large value to the "offset" parameter.
Successful exploitation may allow execution of arbitrary code with the privileges of the web server and bypass the safe_mode restrictions.
8) An unspecified boundary error exists in the "exif_read_data()" function when handling long section names.
9) An error in the "addslashes()" function causes it to not escape NULL bytes correctly. This can e.g. be exploited to read arbitrary files on a system, if the "include()" or "require()" statements partly use user-supplied input.
10) An error within "magic_quotes_gpc" may allow a one-level directory traversal when uploading files with a single quote in the filename (e.g. "..'file.ext").
NOTE: Other potential security issues have also been reported.
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
