CVE-2005-3389
Last modified
CVE-2005-3389 is a vulnerability of currently unknown severity. The parse_str function in PHP 4.x up to 4.4.0 and 5.x up to 5.0.5, when called with only one parameter, allows remote attackers to enable the register_globals directive via inputs that cause a request to be terminated due to the memory_limit setting, which causes PHP to set an internal flag that enables register_globals and allows attackers to exploit vulnerabilities in PHP applications that would otherwise be protected.. EPSS estimates a 6.30% chance of exploitation in the next 30 days.
Description
The parse_str function in PHP 4.x up to 4.4.0 and 5.x up to 5.0.5, when called with only one parameter, allows remote attackers to enable the register_globals directive via inputs that cause a request to be terminated due to the memory_limit setting, which causes PHP to set an internal flag that enables register_globals and allows attackers to exploit vulnerabilities in PHP applications that would otherwise be protected.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Php | Php | 4.0.0 |
| Php | Php | 4.0.1 |
| Php | Php | 4.0.2 |
| Php | Php | 4.0.3 |
| Php | Php | 4.0.4 |
| Php | Php | 4.0.5 |
| Php | Php | 4.0.6 |
| Php | Php | 4.0.7 |
| Php | Php | 4.1.0 |
| Php | Php | 4.1.1 |
| Php | Php | 4.1.2 |
| Php | Php | 4.2 |
| Php | Php | 4.2.0 |
| Php | Php | 4.2.1 |
| Php | Php | 4.2.2 |
| Php | Php | 4.2.3 |
| Php | Php | 4.3.0 |
| Php | Php | 4.3.1 |
| Php | Php | 4.3.2 |
| Php | Php | 4.3.3 |
| Php | Php | 4.3.4 |
| Php | Php | 4.3.5 |
| Php | Php | 4.3.6 |
| Php | Php | 4.3.7 |
| Php | Php | 4.3.8 |
| Php | Php | 4.3.9 |
| Php | Php | 4.3.10 |
| Php | Php | 4.3.11 |
| Php | Php | 4.4.0 |
| Php | Php | 5.0.0 |
| Php | Php | 5.0.1 |
| Php | Php | 5.0.2 |
| Php | Php | 5.0.3 |
| Php | Php | 5.0.4 |
| Php | Php | 5.0.5 |
References
- http://secunia.com/advisories/17371Patch, Vendor Advisory
- http://secunia.com/advisories/17490Vendor Advisory
- http://secunia.com/advisories/17510Vendor Advisory
- http://secunia.com/advisories/17531Vendor Advisory
- http://secunia.com/advisories/17557Vendor Advisory
- http://secunia.com/advisories/17559Vendor Advisory
- http://secunia.com/advisories/18054Vendor Advisory
- http://secunia.com/advisories/18198Vendor Advisory
- http://secunia.com/advisories/18669Vendor Advisory
- http://secunia.com/advisories/21252Vendor Advisory
- http://secunia.com/advisories/22691Vendor Advisory
- http://www.hardened-php.net/advisory_192005.78.htmlVendor Advisory
- http://www.vupen.com/english/advisories/2005/2254Vendor Advisory
- http://www.vupen.com/english/advisories/2006/4320Vendor Advisory
- http://secunia.com/advisories/17371Patch, Vendor Advisory
- http://secunia.com/advisories/17490Vendor Advisory
- http://secunia.com/advisories/17510Vendor Advisory
- http://secunia.com/advisories/17531Vendor Advisory
- http://secunia.com/advisories/17557Vendor Advisory
- http://secunia.com/advisories/17559Vendor Advisory
- http://secunia.com/advisories/18054Vendor Advisory
- http://secunia.com/advisories/18198Vendor Advisory
- http://secunia.com/advisories/18669Vendor Advisory
- http://secunia.com/advisories/21252Vendor Advisory
- http://secunia.com/advisories/22691Vendor Advisory
- http://www.hardened-php.net/advisory_192005.78.htmlVendor Advisory
- http://www.vupen.com/english/advisories/2005/2254Vendor Advisory
- http://www.vupen.com/english/advisories/2006/4320Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2005-3389?
How severe is CVE-2005-3389?
How do I fix CVE-2005-3389?
Are you affected by CVE-2005-3389?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
