# CVE-2008-5519: Information disclosure in n/a

> Remote attackers can obtain sensitive information from Apache Tomcat via specific HTTP requests due to AJP protocol noncompliance.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-5519, DSA-1810-1, GHSA-3v4j-mhgf-pf6w, RHSA-2009:0446, RHSA-2009:1087, RHSA-2009:1618

## What is CVE-2008-5519?

CVE-2008-5519 is a low-severity vulnerability in Apache Tomcat, published on 9 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2008-5519?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mod_jk` | Red Hat:network_satellite:5.1::el4 | All versions | 0:1.2.25-10 |
| `mod_jk-ap20` | Red Hat:network_satellite:5.1::el4 | All versions | 0:1.2.25-10 |
| `mod_jk-debuginfo` | Red Hat:network_satellite:5.1::el4 | All versions | 0:1.2.25-10 |
| `mod_jk` | Red Hat:network_satellite:5.2::el4 | All versions | 0:1.2.25-10 |
| `mod_jk-ap20` | Red Hat:network_satellite:5.2::el4 | All versions | 0:1.2.25-10 |
| `mod_jk-debuginfo` | Red Hat:network_satellite:5.2::el4 | All versions | 0:1.2.25-10 |
| `mod_jk` | Red Hat:rhel_application_server:2 | All versions | 0:1.2.28-1jpp_3rh |
| `mod_jk-ap20` | Red Hat:rhel_application_server:2 | All versions | 0:1.2.28-1jpp_3rh |
| `mod_jk-debuginfo` | Red Hat:rhel_application_server:2 | All versions | 0:1.2.28-1jpp_3rh |
| `mod_jk-manual` | Red Hat:rhel_application_server:2 | All versions | 0:1.2.28-1jpp_3rh |
| `mod_jk` | Red Hat:rhel_application_stack:2 | All versions | 0:1.2.28-1.el5s2 |
| `mod_jk-ap20` | Red Hat:rhel_application_stack:2 | All versions | 0:1.2.28-1.el5s2 |
| `mod_jk-debuginfo` | Red Hat:rhel_application_stack:2 | All versions | 0:1.2.28-1.el5s2 |

Products: Apache Mod Jk, Apache Tomcat.

## How do I fix CVE-2008-5519?

Upgrade to a fixed version.

## Is CVE-2008-5519 being exploited?

There is no known exploitation of CVE-2008-5519 in the wild and no public exploit code.

## Other vulnerabilities in Apache Tomcat

- [CVE-2007-6258](https://insights.sbomify.com/CVE-2007-6258/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5519 and fix it if it is affected.

What it is: CVE-2008-5519 is a low-severity vulnerability in Apache Tomcat, published on 9 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-5519 in the wild and no public exploit code.

Affected product: Apache Tomcat. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-5519/ (Markdown: https://insights.sbomify.com/CVE-2008-5519/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-5519
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-5519
- OSV: https://osv.dev/vulnerability/CVE-2008-5519

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-5519/
Summaries are generated and may contain mistakes; the official description above is the record.