Vulnerability · CVE-2008-5519
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 clien…
Published Apr 9, 2009 · catalog updated Jun 16, 2026 · mod jk
Last checked Nov 3, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2008-5519. EPSS is 7.26%. Act only if a listed version of mod jk is installed.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2007-6258 · High
- Severity
- Low2.6
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 7.26%
- Remediation
- Advisory link
- Affected products
- cpe apache/mod jk
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe apache/mod jk1.2
- cpe apache/mod jk1.2.1
- cpe apache/mod jk1.2.6
- cpe apache/mod jk1.2.7
- cpe apache/mod jk1.2.8
- cpe apache/mod jk1.2.9
How to fix CVE-2008-5519
No stored fix
No vendor fix text is stored. Use the linked advisory before you change production.
Version check
Seen in 1.2 · 5 other packages on the advisory
Advisory
Open the inventory_critical record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2008-5519. EPSS is 7.26%. Act only if a listed version of mod jk is installed.
Which versions are affected?
Compare what you have installed with apache/mod jk 1.2; apache/mod jk 1.2.1; apache/mod jk 1.2.6; apache/mod jk 1.2.7. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-200: Exposure of Sensitive Information. EPSS 7.26%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Apr 9, 2009 · Monitored products — critical
Detected
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
Jun 16, 2026 · Monitored products — critical
Updated
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
Sources
- FIRST EPSSExploitation probabilityCVE-2008-5519
30-day exploitation probability 7.26%
first.org - Monitored products — criticalVendor advisoryCVE-2008-5519
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
nvd.nist.gov
References
Freshness
Last verified in this catalog Nov 3, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 3, 2026
- Monitored products — criticalNov 3, 2026