Strix
26.1K

CVE-2016-6816

UnknownEPSS 39.63%

Last modified

CVE-2016-6816 is a vulnerability of currently unknown severity. The code in Apache Tomcat 9.0.0.M1 to 9.0.0.M11, 8.5.0 to 8.5.6, 8.0.0.RC1 to 8.0.38, 7.0.0 to 7.0.72, and 6.0.0 to 6.0.47 that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. EPSS estimates a 39.63% chance of exploitation in the next 30 days.

Description

The code in Apache Tomcat 9.0.0.M1 to 9.0.0.M11, 8.5.0 to 8.5.6, 8.0.0.RC1 to 8.0.38, 7.0.0 to 7.0.72, and 6.0.0 to 6.0.47 that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack and/or obtain sensitive information from requests other then their own.

Metrics

EPSS Probability
39.63%

98.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
ApacheTomcat6.0.0—
ApacheTomcat6.0.1—
ApacheTomcat6.0.2—
ApacheTomcat6.0.3—
ApacheTomcat6.0.4—
ApacheTomcat6.0.5—
ApacheTomcat6.0.6—
ApacheTomcat6.0.7—
ApacheTomcat6.0.8—
ApacheTomcat6.0.9—
ApacheTomcat6.0.10—
ApacheTomcat6.0.11—
ApacheTomcat6.0.12—
ApacheTomcat6.0.13—
ApacheTomcat6.0.14—
ApacheTomcat6.0.15—
ApacheTomcat6.0.16—
ApacheTomcat6.0.17—
ApacheTomcat6.0.18—
ApacheTomcat6.0.19—
ApacheTomcat6.0.20—
ApacheTomcat6.0.21—
ApacheTomcat6.0.22—
ApacheTomcat6.0.23—
ApacheTomcat6.0.24—
ApacheTomcat6.0.25—
ApacheTomcat6.0.26—
ApacheTomcat6.0.27—
ApacheTomcat6.0.28—
ApacheTomcat6.0.29—
ApacheTomcat6.0.30—
ApacheTomcat6.0.31—
ApacheTomcat6.0.32—
ApacheTomcat6.0.33—
ApacheTomcat6.0.34—
ApacheTomcat6.0.35—
ApacheTomcat6.0.36—
ApacheTomcat6.0.37—
ApacheTomcat6.0.38—
ApacheTomcat6.0.39—
ApacheTomcat6.0.40—
ApacheTomcat6.0.41—
ApacheTomcat6.0.42—
ApacheTomcat6.0.43—
ApacheTomcat6.0.44—
ApacheTomcat6.0.45—
ApacheTomcat6.0.46—
ApacheTomcat6.0.47—
ApacheTomcat7.0.0—
ApacheTomcat7.0.1—

Showing 50 of 168 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-6816?
The code in Apache Tomcat 9.0.0.M1 to 9.0.0.M11, 8.5.0 to 8.5.6, 8.0.0.RC1 to 8.0.38, 7.0.0 to 7.0.72, and 6.0.0 to 6.0.47 that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response. By manipulating the HTTP response the attacker could poison a web-cache, perform an XSS attack and/or obtain sensitive information from requests other then their own.
How severe is CVE-2016-6816?
Severity scoring for CVE-2016-6816 is pending analysis. The EPSS model estimates a 39.63% probability of exploitation in the next 30 days.
How do I fix CVE-2016-6816?
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-6816?

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

Scan your code now

Source: NVD / NIST