CVE-2016-6816
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
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Apache | Tomcat | 6.0.0 | — |
| Apache | Tomcat | 6.0.1 | — |
| Apache | Tomcat | 6.0.2 | — |
| Apache | Tomcat | 6.0.3 | — |
| Apache | Tomcat | 6.0.4 | — |
| Apache | Tomcat | 6.0.5 | — |
| Apache | Tomcat | 6.0.6 | — |
| Apache | Tomcat | 6.0.7 | — |
| Apache | Tomcat | 6.0.8 | — |
| Apache | Tomcat | 6.0.9 | — |
| Apache | Tomcat | 6.0.10 | — |
| Apache | Tomcat | 6.0.11 | — |
| Apache | Tomcat | 6.0.12 | — |
| Apache | Tomcat | 6.0.13 | — |
| Apache | Tomcat | 6.0.14 | — |
| Apache | Tomcat | 6.0.15 | — |
| Apache | Tomcat | 6.0.16 | — |
| Apache | Tomcat | 6.0.17 | — |
| Apache | Tomcat | 6.0.18 | — |
| Apache | Tomcat | 6.0.19 | — |
| Apache | Tomcat | 6.0.20 | — |
| Apache | Tomcat | 6.0.21 | — |
| Apache | Tomcat | 6.0.22 | — |
| Apache | Tomcat | 6.0.23 | — |
| Apache | Tomcat | 6.0.24 | — |
| Apache | Tomcat | 6.0.25 | — |
| Apache | Tomcat | 6.0.26 | — |
| Apache | Tomcat | 6.0.27 | — |
| Apache | Tomcat | 6.0.28 | — |
| Apache | Tomcat | 6.0.29 | — |
| Apache | Tomcat | 6.0.30 | — |
| Apache | Tomcat | 6.0.31 | — |
| Apache | Tomcat | 6.0.32 | — |
| Apache | Tomcat | 6.0.33 | — |
| Apache | Tomcat | 6.0.34 | — |
| Apache | Tomcat | 6.0.35 | — |
| Apache | Tomcat | 6.0.36 | — |
| Apache | Tomcat | 6.0.37 | — |
| Apache | Tomcat | 6.0.38 | — |
| Apache | Tomcat | 6.0.39 | — |
| Apache | Tomcat | 6.0.40 | — |
| Apache | Tomcat | 6.0.41 | — |
| Apache | Tomcat | 6.0.42 | — |
| Apache | Tomcat | 6.0.43 | — |
| Apache | Tomcat | 6.0.44 | — |
| Apache | Tomcat | 6.0.45 | — |
| Apache | Tomcat | 6.0.46 | — |
| Apache | Tomcat | 6.0.47 | — |
| Apache | Tomcat | 7.0.0 | — |
| Apache | Tomcat | 7.0.1 | — |
Showing 50 of 168 affected configurations. See NVD for the full list.
References
- http://www.securityfocus.com/bid/94461Third Party Advisory, VDB Entry
- https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.48Release Notes, Vendor Advisory
- https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.73Release Notes, Vendor Advisory
- https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.39Release Notes, Vendor Advisory
- https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.8Release Notes, Vendor Advisory
- https://tomcat.apache.org/security-9.html#Fixed_in_Apache_Tomcat_9.0.0.M13Release Notes, Vendor Advisory
- http://www.securityfocus.com/bid/94461Third Party Advisory, VDB Entry
- https://tomcat.apache.org/security-6.html#Fixed_in_Apache_Tomcat_6.0.48Release Notes, Vendor Advisory
- https://tomcat.apache.org/security-7.html#Fixed_in_Apache_Tomcat_7.0.73Release Notes, Vendor Advisory
- https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.0.39Release Notes, Vendor Advisory
- https://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.8Release Notes, Vendor Advisory
- https://tomcat.apache.org/security-9.html#Fixed_in_Apache_Tomcat_9.0.0.M13Release Notes, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-6816?
How severe is CVE-2016-6816?
How do I fix CVE-2016-6816?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-6810In Apache ActiveMQ 5.x before 5.14.2, an instance of a cross…
- CVE-2016-6811In Apache Hadoop 2.x before 2.7.4, a user who can escalate t…
- CVE-2016-6812The HTTP transport module in Apache CXF prior to 3.0.12 and …
- CVE-2016-6813Apache CloudStack 4.1 to 4.8.1.0 and 4.9.0.0 contain an API …9.8
- CVE-2016-6814When an application with unsupported Codehaus versions of Gr…
- CVE-2016-6815In Apache Ranger before 0.6.2, users with "keyadmin" role sh…
- CVE-2016-6817The HTTP/2 header parser in Apache Tomcat 9.0.0.M1 to 9.0.0.…7.5
- CVE-2016-6818SQL injection vulnerability in SAP Business Intelligence pla…
- CVE-2016-6820MetroCluster Tiebreaker for clustered Data ONTAP in versions…
- CVE-2016-6823Integer overflow in the BMP coder in ImageMagick before 7.0.…7.5
- CVE-2016-6824Huawei AC6003, AC6005, AC6605, and ACU2 access controllers w…
- CVE-2016-6825Huawei XH620 V3, XH622 V3, and XH628 V3 servers with softwar…
Are you affected by CVE-2016-6816?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST