CVE-2016-10397

UnknownEPSS 1.91%

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

EPSS Probability
1.91%

77.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
PhpPhp<= 5.6.27
PhpPhp7.0.0
PhpPhp7.0.1
PhpPhp7.0.2
PhpPhp7.0.3
PhpPhp7.0.4
PhpPhp7.0.5
PhpPhp7.0.6
PhpPhp7.0.7
PhpPhp7.0.8
PhpPhp7.0.9
PhpPhp7.0.10
PhpPhp7.0.11
PhpPhp7.0.12

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-10397?
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).
How severe is CVE-2016-10397?
Severity scoring for CVE-2016-10397 is pending analysis. The EPSS model estimates a 1.91% probability of exploitation in the next 30 days.
How do I fix CVE-2016-10397?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-10397?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST