CVE-2016-6808

Public Exploit

Description

Buffer overflow in Apache Tomcat Connectors (mod_jk) before 1.2.42.

Category

9.8
CVSS
Severity: Critical
CVSS 3.0 •
CVSS 2.0 •
EPSS 34.23% Top 5%
Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory apache.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
http://www.securitytracker.com/id/1036969 vdb entry third party advisory
http://seclists.org/fulldisclosure/2016/Oct/44 third party advisory mailing list
https://access.redhat.com/errata/RHSA-2017:0194 third party advisory vendor advisory
http://www.securityfocus.com/bid/93429 vdb entry third party advisory
https://access.redhat.com/errata/RHSA-2017:0193 third party advisory vendor advisory
http://rhn.redhat.com/errata/RHSA-2016-2957.html third party advisory vendor advisory
http://tomcat.apache.org/security-jk.html vendor advisory
http://packetstormsecurity.com/files/139071/Apache-Tomcat-JK-ISAPI-Connector-1.2.41-Buffer-Overflow.html mitigation exploit vdb entry third party advisory
http://www.openwall.com/lists/oss-security/2016/10/06/4 third party advisory mailing list
https://lists.apache.org/thread.html/ba661b0edd913b39ff129a32d855620dd861883ade05fd88a8ce517d%40%3Cdev.tomcat.apache.org%3E mailing list
https://lists.apache.org/thread.html/8d2a579bbd977c225c70cb23b0ec54865fb0dab5da3eff1e060c9935%40%3Cdev.tomcat.apache.org%3E mailing list
https://lists.apache.org/thread.html/277d42b48b6e9aef50949c0dcc79ce21693091d73da246b3c1981925%40%3Cdev.tomcat.apache.org%3E mailing list
https://lists.apache.org/thread.html/5b7a23e245c93235c503900da854a143596d901bf1a1f67e851a5de4%40%3Cdev.tomcat.apache.org%3E mailing list
https://lists.apache.org/thread.html/rf8e8c091182b45daa50d3557cad9b10bb4198e3f08cf8f1c66a1b08d%40%3Cdev.tomcat.apache.org%3E mailing list
https://lists.apache.org/thread.html/r5c616dfc49156e4b06ffab842800c80f4425924d0f20c452c127a53c%40%3Cdev.tomcat.apache.org%3E mailing list

Frequently Asked Questions

What is the severity of CVE-2016-6808?
CVE-2016-6808 has been scored as a critical severity vulnerability.
How to fix CVE-2016-6808?
To fix CVE-2016-6808, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-6808 being actively exploited in the wild?
It is possible that CVE-2016-6808 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~34% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.