CVE-2009-3869

HIGHCVSS v2 · 9.39.3
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 9.3 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:M/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 65% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Weaponized
9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 65%
  • Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 65%CVSS v2: 9.3Exploit: Metasploit · Exploit-DB (verified)Exposed services: Not assessed

A fix is available — apply it.

Stack-based buffer overflow in the setDiffICM function in the Abstract Window Toolkit (AWT) in Java Runtime Environment (JRE) 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 execute arbitrary code via a crafted argument, aka Bug Id 6872357.

CVSS v2.0 (legacy)
9.3HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
9.3HIGHlow confidence
EG Risk
68
EG Risk 68/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
The EG Score, 9.3 of 10.
Exploitation65% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
65%
EPSS %ILE
99th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 5, 2009

Last Modified

April 23, 2026

References (27)

15 of 27 shown · show the other 12

Vendor Advisories for CVE-2009-3869(2)

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

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenjdk-6-jre (6b16-1.6.1-3ubuntu1) @ karmic2026-05-30ubuntu
redhatjava-1.4.2-ibm-0:1.4.2.13.4.sap-1jpp.1.el52010-05-12redhat
redhatjava-1.6.0-ibm-1:1.6.0.7-1jpp.2.el52010-01-14redhat
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

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(7)

Data Freshness Timeline

(refreshed 6× in last 7d / 15× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 22 repeat rows among the latest 94 are merged into the row they repeat.

  1. 2026-10-12 01:51 UTCEG score recompute
  2. 2026-10-11 13:38 UTCEPSS rescoreEPSS 65% · 99th percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 65% · 99th percentile
  4. 2026-10-09 20:00 UTCEPSS rescoreEPSS 65% · 99th percentile
  5. 2026-10-07 23:37 UTCEPSS rescoreEPSS 65% · 99th percentile
  6. 2026-10-06 15:09 UTCEPSS rescoreEPSS 65% · 99th percentile
  7. 2026-09-30 14:58 UTCEPSS rescoreEPSS 65% · 99th percentile
  8. 2026-09-29 08:01 UTCEG score recompute
  9. 2026-09-27 13:39 UTCEPSS rescoreEPSS 65% · 99th percentile
  10. 2026-09-26 15:52 UTCEPSS rescoreEPSS 65% · 99th percentile
  11. 2026-09-24 13:57 UTCEPSS rescoreEPSS 65% · 99th percentile
  12. 2026-09-17 19:20 UTCEPSS rescoreEPSS 65% · 99th percentile
  13. 2026-09-15 03:04 UTCEPSS rescoreEPSS 65% · 99th percentile
  14. 2026-09-13 16:40 UTCEPSS rescoreEPSS 65% · 99th percentile
  15. 2026-09-12 14:54 UTCEPSS rescoreEPSS 65% · 99th percentile
  16. 2026-09-10 09:24 UTCEPSS rescoreEPSS 65% · 99th percentile
  17. 2026-09-06 13:41 UTCEPSS rescoreEPSS 65% · 99th percentile
  18. 2026-09-05 15:22 UTCEPSS rescoreEPSS 65% · 99th percentile
  19. 2026-09-04 13:55 UTCEPSS rescoreEPSS 65% · 99th percentile
  20. 2026-08-28 21:34 UTCEPSS rescoreEPSS 65% · 99th percentile
  21. 2026-08-19 16:58 UTCEPSS rescoreEPSS 65% · 99th percentile
  22. 2026-08-15 01:24 UTCEPSS rescoreEPSS 65% · 99th percentile
  23. 2026-08-09 13:41 UTCEPSS rescoreEPSS 65% · 99th percentile
  24. 2026-08-03 10:28 UTCEPSS rescoreEPSS 65% · 99th percentile
  25. 2026-07-30 16:22 UTCEPSS rescoreEPSS 65% · 99th percentile
Show 47 more
  1. 2026-07-30 01:26 UTCEPSS rescoreEPSS 65% · 99th percentile
  2. 2026-07-26 13:39 UTCEG score recomputeAssessed again: 9.3 HIGH
  3. 2026-07-25 14:12 UTCEPSS rescoreEPSS 65% · 99th percentile
  4. 2026-07-24 14:12 UTCEPSS rescoreEPSS 65% · 99th percentile
  5. 2026-07-23 14:14 UTCEPSS rescoreEPSS 65% · 99th percentile
  6. 2026-07-23 01:00 UTCEG score recompute
  7. 2026-07-23 00:37 UTCEG score recompute▼ 5.80
  8. 2026-07-23 00:04 UTCEG score recomputeFirst assessed: 5.8 MEDIUM
  9. 2026-07-22 21:43 UTCEG score recompute
  10. 2026-07-22 14:03 UTCEPSS rescoreEPSS 65% · 99th percentile
  11. 2026-07-21 15:20 UTCEPSS rescoreEPSS 65% · 99th percentile
  12. 2026-07-20 17:03 UTCEPSS rescoreEPSS 65% · 99th percentile
  13. 2026-07-18 09:59 UTCEPSS rescoreEPSS 65% · 99th percentile
  14. 2026-07-15 16:54 UTCEPSS rescoreEPSS 65% · 99th percentile
  15. 2026-07-15 01:55 UTCEPSS rescoreEPSS 65% · 99th percentile
  16. 2026-07-13 06:07 UTCEPSS rescoreEPSS 65% · 99th percentile
  17. 2026-07-11 08:22 UTCEPSS rescoreEPSS 65% · 99th percentile
  18. 2026-07-09 19:04 UTCEPSS rescoreEPSS 65% · 99th percentile
  19. 2026-07-06 16:23 UTCEPSS rescoreEPSS 65% · 99th percentile
  20. 2026-07-05 02:26 UTCEPSS rescoreEPSS 65% · 99th percentile
  21. 2026-07-01 15:02 UTCEPSS rescoreEPSS 65% · 99th percentile
  22. 2026-06-28 04:52 UTCEPSS rescoreEPSS 65% · 99th percentile
  23. 2026-06-27 03:05 UTCEPSS rescoreEPSS 65% · 99th percentile
  24. 2026-06-25 13:46 UTCEPSS rescoreEPSS 65% · 99th percentile
  25. 2026-06-23 21:29 UTCEPSS rescoreEPSS 65% · 99th percentile
  26. 2026-06-21 01:56 UTCEPSS rescoreEPSS 65% · 99th percentile
  27. 2026-06-18 17:49 UTCEPSS rescoreEPSS 65% · 99th percentile
  28. 2026-06-17 17:49 UTCEPSS rescoreEPSS 65% · 99th percentile
  29. 2026-06-16 17:49 UTCEPSS rescoreEPSS 65% · 99th percentile
  30. 2026-06-15 17:44 UTCEPSS rescoreEPSS 65% · 99th percentile
  31. 2026-06-12 23:08 UTCEPSS rescoreEPSS 78% · 99th percentile
  32. 2026-06-10 22:14 UTCEPSS rescoreEPSS 78% · 99th percentile
  33. 2026-06-07 15:22 UTCEPSS rescoreEPSS 78% · 99th percentile
  34. 2026-06-06 13:44 UTCEPSS rescoreEPSS 78% · 99th percentile
  35. 2026-06-05 22:44 UTCEPSS rescoreEPSS 78% · 99th percentile
  36. 2026-06-05 06:07 UTCEPSS rescoreEPSS 78% · 99th percentile
  37. 2026-06-04 13:09 UTCEPSS rescoreEPSS 78% · 99th percentile
  38. 2026-06-02 20:10 UTCEPSS rescoreEPSS 78% · 99th percentile
  39. 2026-06-01 13:49 UTCEPSS rescoreEPSS 78% · 99th percentile
  40. 2026-05-31 00:13 UTCEPSS rescoreEPSS 78% · 99th percentile
  41. 2026-05-30 14:42 UTCEG score recompute
  42. 2026-05-30 14:42 UTCVendor advisory
  43. 2026-05-30 14:42 UTCGHSA enrichmentGHSA-xf34-q2g4-cjm6 · GitHub severity HIGH
  44. 2026-05-29 13:40 UTCEPSS rescoreEPSS 78% · 99th percentile
  45. 2026-05-22 21:15 UTCEPSS rescoreEPSS 78% · 99th percentile
  46. 2026-05-20 22:37 UTCEPSS rescoreEPSS 78% · 99th percentile
  47. 2026-05-18 21:29 UTCEPSS rescoreEPSS 78% · 99th percentile

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-16298✓ verified
    Published Sep 20, 2010

    Sun Java - JRE AWT setDiffICM Buffer Overflow (Metasploit)

    Open source ↗
  • Metasploitexploit/multi/browser/java_setdifficm_bof✓ verified
    Published Dec 17, 2009

    Sun Java JRE AWT setDiffICM Buffer Overflow

    Open source ↗

Frequently asked(4)

What is CVE-2009-3869?
CVE-2009-3869 is a high-severity vulnerability; its CVE record was published on November 5, 2009. Stack-based buffer overflow in the setDiffICM function in the Abstract Window Toolkit (AWT) in Java Runtime Environment (JRE) 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…
When was CVE-2009-3869 made public?
CVE-2009-3869 was made public on November 3, 2009: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on November 5, 2009. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2009-3869 actively exploited?
CVE-2009-3869 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 65% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2009-3869?
A fix for CVE-2009-3869 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2009-3869 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2009-3869?

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