CVE-2008-5519
Last modified
CVE-2008-5519 is a vulnerability of currently unknown severity. The JK Connector (aka mod_jk) 1.2.0 through 1.2.26 in Apache Tomcat allows remote attackers to obtain sensitive information via an arbitrary request from an HTTP client, in opportunistic circumstances involving (1) a request from a different client that included a Content-Length header but no POST data or (2) a rapid series of requests, related to noncompliance with the AJP protocol's requirements for requests containing Content-Length headers.. EPSS estimates a 7.26% chance of exploitation in the next 30 days.
Description
The JK Connector (aka mod_jk) 1.2.0 through 1.2.26 in Apache Tomcat allows remote attackers to obtain sensitive information via an arbitrary request from an HTTP client, in opportunistic circumstances involving (1) a request from a different client that included a Content-Length header but no POST data or (2) a rapid series of requests, related to noncompliance with the AJP protocol's requirements for requests containing Content-Length headers.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Apache | Mod Jk | 1.2 |
| Apache | Mod Jk | 1.2.1 |
| Apache | Mod Jk | 1.2.6 |
| Apache | Mod Jk | 1.2.7 |
| Apache | Mod Jk | 1.2.8 |
| Apache | Mod Jk | 1.2.9 |
| Apache | Mod Jk | 1.2.10 |
| Apache | Mod Jk | 1.2.11 |
| Apache | Mod Jk | 1.2.12 |
| Apache | Mod Jk | 1.2.13 |
| Apache | Mod Jk | 1.2.14 |
| Apache | Mod Jk | 1.2.14.1 |
| Apache | Mod Jk | 1.2.15 |
| Apache | Mod Jk | 1.2.16 |
| Apache | Mod Jk | 1.2.17 |
| Apache | Mod Jk | 1.2.18 |
| Apache | Mod Jk | 1.2.19 |
| Apache | Mod Jk | 1.2.20 |
| Apache | Mod Jk | 1.2.21 |
| Apache | Mod Jk | 1.2.22 |
| Apache | Mod Jk | 1.2.23 |
| Apache | Mod Jk | 1.2.24 |
| Apache | Mod Jk | 1.2.25 |
| Apache | Mod Jk | 1.2.26 |
| Apache | Tomcat | 4.0.0 |
| Apache | Tomcat | 4.0.1 |
| Apache | Tomcat | 4.0.2 |
| Apache | Tomcat | 4.0.3 |
| Apache | Tomcat | 4.0.4 |
| Apache | Tomcat | 4.0.5 |
| Apache | Tomcat | 4.0.6 |
| Apache | Tomcat | 4.1.0 |
| Apache | Tomcat | 4.1.1 |
| Apache | Tomcat | 4.1.2 |
| Apache | Tomcat | 4.1.3 |
| Apache | Tomcat | 4.1.4 |
| Apache | Tomcat | 4.1.5 |
| Apache | Tomcat | 4.1.6 |
| Apache | Tomcat | 4.1.7 |
| Apache | Tomcat | 4.1.8 |
| Apache | Tomcat | 4.1.9 |
| Apache | Tomcat | 4.1.10 |
| Apache | Tomcat | 4.1.11 |
| Apache | Tomcat | 4.1.12 |
| Apache | Tomcat | 4.1.13 |
| Apache | Tomcat | 4.1.14 |
| Apache | Tomcat | 4.1.15 |
| Apache | Tomcat | 4.1.16 |
| Apache | Tomcat | 4.1.17 |
| Apache | Tomcat | 4.1.18 |
Showing 50 of 126 affected configurations. See NVD for the full list.
References
- http://secunia.com/advisories/34621Vendor Advisory
- http://svn.eu.apache.org/viewvc?view=rev&revision=702540Vendor Advisory
- http://tomcat.apache.org/security-jk.htmlVendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=490201Vendor Advisory
- http://secunia.com/advisories/34621Vendor Advisory
- http://svn.eu.apache.org/viewvc?view=rev&revision=702540Vendor Advisory
- http://tomcat.apache.org/security-jk.htmlVendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=490201Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2008-5519?
How severe is CVE-2008-5519?
How do I fix CVE-2008-5519?
Are you affected by CVE-2008-5519?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
