CVE-2009-3877

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 5%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

Unspecified vulnerability in Sun Java SE in JDK and JRE 5.0 before Update 22, JDK and JRE 6 before Update 17, SDK and JRE 1.3.x before 1.3.1_27, and SDK and JRE 1.4.x before 1.4.2_24 allows remote attackers to cause a denial of service (memory consumption) via crafted HTTP headers, which are not properly parsed by the ASN.1 DER input stream parser, aka Bug Id 6864911.

CVSS v3
—
EG Score
0.0(none)
EPSS
90.9%
KEV
Not listed

Published

November 5, 2009

Last Modified

April 23, 2026

References (48)

Vendor Advisories for CVE-2009-3877(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenjdk-6-jre (6b12-0ubuntu6.6) @ intrepid2026-05-30ubuntu
redhatjava-1.6.0-ibm-1:1.6.0.7-1jpp.2.el52010-01-14redhat
redhatjava-1.5.0-sun-0:1.5.0.22-1jpp.1.el42009-12-11redhat
redhatjava-1.4.2-ibm-0:1.4.2.13.3-1jpp.1.el52009-12-08redhat
redhatjava-1.5.0-ibm-1:1.5.0.11-1jpp.1.el52009-12-08redhat
redhatjava-1.6.0-openjdk-1:1.6.0.0-1.7.b09.el52009-11-16redhat
redhatjava-1.5.0-sun-0:1.5.0.22-1jpp.1.el52009-11-10redhat
redhatjava-1.6.0-sun-1:1.6.0.17-1jpp.2.el52009-11-09redhat
redhatjava-1.4.2-ibm-0:1.4.2.13.2.sap-1jpp.4.el5_32009-11-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Additional Vendor Advisories

(9)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:23 UTCEPSS rescore
  2. 2026-07-06 02:19 UTCEPSS rescore
  3. 2026-07-06 02:19 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-05 02:26 UTCEPSS rescore
  6. 2026-07-04 06:27 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-29 14:02 UTCEPSS rescore
  10. 2026-06-29 14:02 UTCEPSS rescore
  11. 2026-06-28 04:52 UTCEPSS rescore
  12. 2026-06-28 04:52 UTCEPSS rescore
  13. 2026-06-27 03:05 UTCEPSS rescore
  14. 2026-06-25 13:46 UTCEPSS rescore
  15. 2026-06-25 13:46 UTCEPSS rescore
  16. 2026-06-24 14:02 UTCEPSS rescore
  17. 2026-06-24 14:02 UTCEPSS rescore
  18. 2026-06-23 21:29 UTCEPSS rescore
  19. 2026-06-23 21:29 UTCEPSS rescore
  20. 2026-06-22 14:22 UTCEPSS rescore
  21. 2026-06-22 14:22 UTCEPSS rescore
  22. 2026-06-21 14:53 UTCEPSS rescore
  23. 2026-06-21 01:56 UTCEPSS rescore
  24. 2026-06-21 01:56 UTCEPSS rescore
  25. 2026-06-19 19:22 UTCEPSS rescore
Show 46 more
  1. 2026-06-19 19:22 UTCEPSS rescore
  2. 2026-06-18 17:49 UTCEPSS rescore
  3. 2026-06-18 17:49 UTCEPSS rescore
  4. 2026-06-17 17:49 UTCEPSS rescore
  5. 2026-06-17 17:49 UTCEPSS rescore
  6. 2026-06-16 17:49 UTCEPSS rescore
  7. 2026-06-16 17:49 UTCEPSS rescore
  8. 2026-06-15 17:44 UTCEPSS rescore
  9. 2026-06-14 23:14 UTCEPSS rescore
  10. 2026-06-14 23:14 UTCEPSS rescore
  11. 2026-06-13 22:57 UTCEPSS rescore
  12. 2026-06-12 23:08 UTCEPSS rescore
  13. 2026-06-12 23:08 UTCEPSS rescore
  14. 2026-06-10 22:14 UTCEPSS rescore
  15. 2026-06-10 13:17 UTCEPSS rescore
  16. 2026-06-08 14:13 UTCEPSS rescore
  17. 2026-06-07 15:22 UTCEPSS rescore
  18. 2026-06-07 15:22 UTCEPSS rescore
  19. 2026-06-05 22:44 UTCEPSS rescore
  20. 2026-06-05 22:44 UTCEPSS rescore
  21. 2026-06-05 06:07 UTCEPSS rescore
  22. 2026-06-04 13:09 UTCEPSS rescore
  23. 2026-06-04 13:09 UTCEPSS rescore
  24. 2026-06-02 20:10 UTCEPSS rescore
  25. 2026-06-02 20:10 UTCEPSS rescore
  26. 2026-05-31 22:28 UTCEPSS rescore
  27. 2026-05-31 22:28 UTCEPSS rescore
  28. 2026-05-31 00:13 UTCEPSS rescore
  29. 2026-05-31 00:13 UTCEPSS rescore
  30. 2026-05-30 14:41 UTCEG score recompute
  31. 2026-05-30 14:41 UTCVendor advisory
  32. 2026-05-30 14:41 UTCGHSA enrichment
  33. 2026-05-29 13:40 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-27 13:38 UTCEPSS rescore
  39. 2026-05-24 16:43 UTCEPSS rescore
  40. 2026-05-22 21:15 UTCEPSS rescore
  41. 2026-05-22 21:15 UTCEPSS rescore
  42. 2026-05-20 22:37 UTCEPSS rescore
  43. 2026-05-20 22:37 UTCEPSS rescore
  44. 2026-05-20 11:21 UTCEPSS rescore
  45. 2026-05-20 11:20 UTCEPSS rescore
  46. 2026-05-18 21:29 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2009-3877?
CVE-2009-3877 is a none vulnerability published on November 5, 2009. Unspecified vulnerability in Sun Java SE in JDK and JRE 5.0 before Update 22, JDK and JRE 6 before Update 17, SDK and JRE 1.3.x before 1.3.127, and SDK and JRE 1.4.x before 1.4.224 allows remote attackers to cause a denial of service (memory consumption) via crafted HTTP headers, which are not…
When was CVE-2009-3877 disclosed?
CVE-2009-3877 was first published in the National Vulnerability Database on November 5, 2009, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2009-3877 actively exploited?
CVE-2009-3877 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2009-3877?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-3877, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2009-3877

Explore →

Is Your Infrastructure Affected by CVE-2009-3877?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs