CVE-2007-3205
Summary
| CVE | CVE-2007-3205 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2007-06-13 10:30:00 UTC |
| Updated | 2018-10-16 16:47:00 UTC |
| Description | The parse_str function in (1) PHP, (2) Hardened-PHP, and (3) Suhosin, when called without a second parameter, might allow remote attackers to overwrite arbitrary variables by specifying variable names and values in the string to be parsed. NOTE: it is not clear whether this is a design limitation of the function or a bug in PHP, although it is likely to be regarded as a bug in Hardened-PHP and Suhosin. |
Risk And Classification
Problem Types: NVD-CWE-Other
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Hardened-php Project | Hardened-php | All | All | All | All |
| Application | Hardened-php Project | Hardened-php | All | All | All | All |
| Application | Hardened-php Project | Subhosin | All | All | All | All |
| Application | Hardened-php Project | Subhosin | All | All | All | All |
| Application | Php | Php | All | All | All | All |
| Application | Php | Php | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| www.acid-root.new.fr/advisories/14070612.txt | MISC | www.acid-root.new.fr | |
| SecurityReason - PHP parse_str() arbitrary variable overwrite | SREASON | securityreason.com | |
| 39834 | OSVDB | osvdb.org | |
| SecurityFocus | BUGTRAQ | www.securityfocus.com | |
| SecurityFocus | BUGTRAQ | www.securityfocus.com | |
| SecurityFocus | BUGTRAQ | www.securityfocus.com | |
| IBM X-Force Exchange | XF | exchange.xforce.ibmcloud.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
| Organization | Published | Contributor | Statement |
|---|---|---|---|
| Red Hat | 2007-06-26 | Mark J Cox | This is not a security vulnerability: it is the expected behaviour of parse_str when used without a second parameter. |