Contents
- Vital information on this issue
- Scanning For and Finding Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13
- Penetration Testing (Pentest) for this Vulnerability
- Security updates on Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13
- Disclosures related to Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13
- Confirming the Presence of Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13
- False positive/negatives
- Patching/Repairing this vulnerability
- Exploits related to Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13
Information on PHP 5.3.2 Vulnerability/Exploit
Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13 is a high risk vulnerability that is one of the most frequently found on networks around the world. This issue has been around since at least 1990 but has proven either difficult to detect, difficult to resolve or prone to being overlooked entirely.
| Vulnerability Name: | PHP Running Version Prior to 5.3.2 / 5.2.13 |
| Test ID: | 12257 |
| Rest: | High |
| Category: | Server-Side Scripts |
| Type: | Attack |
| Summary: | Multiple vulnerabilities have been found in PHP: * The Linear Congruential Generator (LCG) in PHP before 5.2.13 does not provide the expected entropy, which makes it easier for context-dependent attackers to guess values that were intended to be unpredictable, as demonstrated by session cookies generated by using the uniqid function. * The safe_mode implementation in PHP before 5.2.13 does not properly handle directory pathnames that lack a trailing / (slash) character, which allows context-dependent attackers to bypass intended access restrictions via vectors related to use of the tempnam function. * session.c in the session extension in PHP before 5.2.13, and 5.3.1, does not properly interpret ; (semicolon) characters in the argument to the session_save_path function, which allows context-dependent attackers to bypass open_basedir and safe_mode restrictions via an argument that contains multiple ; characters in conjunction with a .. (dot dot). |
| Impact: | |
| Solution: | Upgrade to PHP version 5.3.2, PHP version 5.2.13 or newer. |
| CVE: | CVE-2010-1128 CVE-2010-1129 2010-1130 |
| More Information: | http://samy.pl/phpwn/ http://cxsecurity.com/issue/WLB-2010020063 https://cxsecurity.com/issue/WLB-2010020063 http://www.php.net/ChangeLog-5.php#5.2.13 http://www.php.net/ChangeLog-5.php#5.3.2 http://php.net/releases/5_2_13.php http://php.net/releases/5_3_2.php |
| Nist NVD (CVSS): | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| CVSS Score: | 7.5 |
Scanning For and Finding Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13
Use of Vulnerability Management tools, like AVDS, are standard practice for the discovery of this vulnerability. The primary failure of VA in finding this vulnerability is related to setting the proper scope and frequency of network scans. It is vital that the broadest range of hosts (active IPs) possible are scanned and that scanning is done frequently. We recommend weekly. Your existing scanning solution or set of test tools should make this not just possible, but easy and affordable. If that is not the case, please consider AVDS.
Penetration Testing (pentest) PHP
The Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13 is prone to false positive reports by most vulnerability assessment solutions. AVDS is alone in using behavior based testing that eliminates this issue. For all other VA tools security consultants will recommend confirmation by direct observation. In any case Penetration testing procedures for discovery of Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13 produces the highest discovery accuracy rate, but the infrequency of this expensive form of testing degrades its value. The ideal would be to have pentesting accuracy and the frequency and scope possibilities of VA solutions, and this is accomplished only by AVDS.
Security Updates on Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13
Given that this is one of the most frequently found vulnerabilities, there is ample information regarding mitigation online and very good reason to get it fixed. Hackers are also aware that this is a frequently found vulnerability and so its discovery and repair is that much more important. It is so well known and common that any network that has it present and unmitigated indicates “low hanging fruit” to attackers.
Confirming the Presence of Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13
Confirming the Presence of Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13
False positive/negatives
The secret killer of VA solution value is the false positive. There was an industry wide race to find the most vulnerabilities, including Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13 ,and this resulted in benefit to poorly written tests that beef up scan reports by adding a high percentage of uncertainty. This may have sold a lot of systems some years ago, but it also stuck almost all VA solutions with deliberately inaccurate reporting that adds time to repairs that no administrator can afford. Beyond Security did not participate in this race to mutually assured destruction of the industry and to this day produces the most accurate and actionable reports available.
Patching/Repairing this Vulnerability
Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13 is a high risk vulnerability that is also high frequency and high visibility. This is the most severe combination of security factors that exists and it is extremely important to find it on your network and fix it as soon as possible.
Exploits related to Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13
Exploits related to Vulnerabilities in PHP Running Version Prior to 5.3.2 / 5.2.13