CVE-2016-10397
Last modified
CVE-2016-10397 is a vulnerability of currently unknown severity. In PHP before 5.6.28 and 7.x before 7.0.13, incorrect handling of various URI components in the URL parser could be used by attackers to bypass hostname-specific URL checks, as demonstrated by evil.example.com:80#@good.example.com/ and evil.example.com:80?@good.example.com/ inputs to the parse_url function (implemented in the php_url_parse_ex function in ext/standard/url.c).. EPSS estimates a 1.91% chance of exploitation in the next 30 days.
Description
In PHP before 5.6.28 and 7.x before 7.0.13, incorrect handling of various URI components in the URL parser could be used by attackers to bypass hostname-specific URL checks, as demonstrated by evil.example.com:80#@good.example.com/ and evil.example.com:80?@good.example.com/ inputs to the parse_url function (implemented in the php_url_parse_ex function in ext/standard/url.c).
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Php | Php | <= 5.6.27 |
| Php | Php | 7.0.0 |
| Php | Php | 7.0.1 |
| Php | Php | 7.0.2 |
| Php | Php | 7.0.3 |
| Php | Php | 7.0.4 |
| Php | Php | 7.0.5 |
| Php | Php | 7.0.6 |
| Php | Php | 7.0.7 |
| Php | Php | 7.0.8 |
| Php | Php | 7.0.9 |
| Php | Php | 7.0.10 |
| Php | Php | 7.0.11 |
| Php | Php | 7.0.12 |
References
- http://openwall.com/lists/oss-security/2017/07/10/6Mailing List, Patch, Third Party Advisory
- http://php.net/ChangeLog-5.phpRelease Notes, Vendor Advisory
- http://php.net/ChangeLog-7.phpRelease Notes, Vendor Advisory
- https://bugs.php.net/bug.php?id=73192Issue Tracking, Third Party Advisory
- http://openwall.com/lists/oss-security/2017/07/10/6Mailing List, Patch, Third Party Advisory
- http://php.net/ChangeLog-5.phpRelease Notes, Vendor Advisory
- http://php.net/ChangeLog-7.phpRelease Notes, Vendor Advisory
- https://bugs.php.net/bug.php?id=73192Issue Tracking, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-10397?
How severe is CVE-2016-10397?
How do I fix CVE-2016-10397?
Are you affected by CVE-2016-10397?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
