Skip to content
Noroxi
CVE-2008-5519· NVD / CVE Program· CNA redhat

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

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.

LowCVSS 2.6 · v2.0—No exploit Fix available
Published
Apr 9, 2009
Updated
Jun 16, 2026
EPSS
7.3% · 94th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

12

Monitor

Low priority for now.

CVSS
10 / 40 · 2.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 7.3%

Affected systems

VendorProduct
apachemod jk
apachetomcat

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache mod jk1.2
  • apache mod jk1.2.1
  • apache mod jk1.2.10
  • apache mod jk1.2.11
  • apache mod jk1.2.12
  • apache mod jk1.2.13
  • apache mod jk1.2.14
  • apache mod jk1.2.14.1
  • apache mod jk1.2.15
  • apache mod jk1.2.16
  • apache mod jk1.2.17
  • apache mod jk1.2.18
  • apache mod jk1.2.19
  • apache mod jk1.2.20
  • apache mod jk1.2.21
  • apache mod jk1.2.22
  • apache mod jk1.2.23
  • apache mod jk1.2.24
  • apache mod jk1.2.25
  • apache mod jk1.2.26

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12libapache-mod-jkbefore 1:1.2.26-2.11:1.2.26-2.1
Debian:4.0libapache-mod-jkbefore 1:1.2.18-3etch21:1.2.18-3etch2
Debian:5.0libapache-mod-jkbefore 1:1.2.26-2+lenny11:1.2.26-2+lenny1
openSUSE:Tumbleweedapache2-mod_jkbefore 1.2.41-1.51.2.41-1.5
Red Hat:network_satellite:5.1::el4mod_jkbefore 0:1.2.25-100:1.2.25-10
Red Hat:network_satellite:5.1::el4mod_jk-ap20before 0:1.2.25-100:1.2.25-10
Red Hat:network_satellite:5.1::el4mod_jk-debuginfobefore 0:1.2.25-100:1.2.25-10
Red Hat:rhel_application_server:2mod_jkbefore 0:1.2.28-1jpp_3rh0:1.2.28-1jpp_3rh
Red Hat:rhel_application_server:2mod_jk-ap20before 0:1.2.28-1jpp_3rh0:1.2.28-1jpp_3rh
Red Hat:rhel_application_server:2mod_jk-debuginfobefore 0:1.2.28-1jpp_3rh0:1.2.28-1jpp_3rh
Red Hat:rhel_application_server:2mod_jk-manualbefore 0:1.2.28-1jpp_3rh0:1.2.28-1jpp_3rh
Red Hat:rhel_application_stack:2mod_jkbefore 0:1.2.28-1.el5s20:1.2.28-1.el5s2
Red Hat:rhel_application_stack:2mod_jk-ap20before 0:1.2.28-1.el5s20:1.2.28-1.el5s2
Red Hat:rhel_application_stack:2mod_jk-debuginfobefore 0:1.2.28-1.el5s20:1.2.28-1.el5s2

Other highest-scoring records for the same primary product.

  • CVE-2007-6258Multiple stack-based buffer overflows in the legacy mod_jk2 2.0.3-DEV and earlier Apache module allow remote attackers to execute arbitrary
    42Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:libapache-mod-jk1:1.2.26-2.1 · Debian:12Package registry (OSV)
opensuse:apache2-mod_jk1.2.41-1.5 · openSUSE:TumbleweedPackage registry (OSV)
red hat:mod_jk0:1.2.28-1.el5s2 · Red Hat:rhel_application_stack:2Package registry (OSV)
red hat:mod_jk-ap200:1.2.28-1.el5s2 · Red Hat:rhel_application_stack:2Package registry (OSV)
red hat:mod_jk-debuginfo0:1.2.28-1.el5s2 · Red Hat:rhel_application_stack:2Package registry (OSV)
red hat:mod_jk-manual0:1.2.28-1jpp_3rh · Red Hat:rhel_application_server:2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
P · data can be read
Integrity
none
Availability
none
Attack complexity
High
Confidentiality impact
P
Integrity impact
None
Availability impact
None

CVSS vector

AV:N/AC:H/Au:N/C:P/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records