CVE-2009-0217

MEDIUMCVSS v2 · 5.05.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:N/I:P/A:N. 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 6.4% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 6.4%CVSS v2: 5.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The design of the W3C XML Signature Syntax and Processing (XMLDsig) recommendation, as implemented in products including (1) the Oracle Security Developer Tools component in Oracle Application Server 10.1.2.3, 10.1.3.4, and 10.1.4.3IM; (2) the WebLogic Server component in BEA Product Suite 10.3, 10.0 MP1, 9.2 MP3, 9.1, 9.0, and 8.1 SP6; (3) Mono before 2.4.2.2; (4) XML Security Library before 1.2.12; (5) IBM WebSphere Application Server Versions 6.0 through 6.0.2.33, 6.1 through 6.1.0.23, and 7.0 through 7.0.0.1; (6) Sun JDK and JRE Update 14 and earlier; (7) Microsoft .NET Framework 3.0 through 3.0 SP2, 3.5, and 4.0; and other products uses a parameter that defines an HMAC truncation length (HMACOutputLength) but does not require a minimum for this length, which allows attackers to spoof HMAC-based signatures and bypass authentication by specifying a truncation length with a small number of bits.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0MEDIUMlow confidence
EG Risk
30
EG Risk 30/100CISA SSVC

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
Severity50% × 45%
Exploitation6% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
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
6.4%
EPSS %ILE
93rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

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

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 14, 2009

Last Modified

April 23, 2026

References (172)

Vendor Advisories for CVE-2009-0217(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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenoffice.org-core (1:3.1.1-5ubuntu1.1) @ karmic2026-05-30ubuntu
ubuntuopenjdk-6-jre (6b14-1.4.1-0ubuntu11) @ jaunty2026-05-30ubuntu
ubuntulibmono-security1.0-cil (2.0.1-4ubuntu0.1) @ jaunty2026-05-30ubuntu
redhatjava-1.6.0-ibm-1:1.6.0.7-1jpp.2.el52010-01-14redhat
redhatxml-security-0:1.3.0-1.3.patch01.ep1.2.1.el52009-12-10redhat
redhatxml-security-0:1.3.0-1.3.patch01.ep1.2.el42009-12-09redhat
redhatxmlsec1-0:1.2.9-8.1.12009-09-08redhat
redhatjava-1.6.0-openjdk-1:1.6.0.0-1.2.b09.el52009-08-06redhat
redhatjava-1.6.0-sun-1:1.6.0.15-1jpp.1.el52009-08-06redhat

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.

Affected Packages

(18 across 8 ecosystems)
Debian:11(3)
PackageVulnerable rangeFix by version rangeDependents
mono—
  • every version up to 2.4.2.3+dfsg-1: fixed in 2.4.2.3+dfsg-1
—
xmlsec1—
  • every version up to 1.2.12-1: fixed in 1.2.12-1
—
xml-security-c—
  • every version up to 1.4.0-4: fixed in 1.4.0-4
—
Debian:12(3)
PackageVulnerable rangeFix by version rangeDependents
mono—
  • every version up to 2.4.2.3+dfsg-1: fixed in 2.4.2.3+dfsg-1
—
xmlsec1—
  • every version up to 1.2.12-1: fixed in 1.2.12-1
—
xml-security-c—
  • every version up to 1.4.0-4: fixed in 1.4.0-4
—
Debian:13(3)
PackageVulnerable rangeFix by version rangeDependents
mono—
  • every version up to 2.4.2.3+dfsg-1: fixed in 2.4.2.3+dfsg-1
—
xmlsec1—
  • every version up to 1.2.12-1: fixed in 1.2.12-1
—
xml-security-c—
  • every version up to 1.4.0-4: fixed in 1.4.0-4
—
Debian:14(3)
PackageVulnerable rangeFix by version rangeDependents
mono—
  • every version up to 2.4.2.3+dfsg-1: fixed in 2.4.2.3+dfsg-1
—
xmlsec1—
  • every version up to 1.2.12-1: fixed in 1.2.12-1
—
xml-security-c—
  • every version up to 1.4.0-4: fixed in 1.4.0-4
—
Debian:4.0(2)
PackageVulnerable rangeFix by version rangeDependents
openoffice.org2.0.4.dfsg.2-5etch1 ... 2.0.4.dfsg.2-7etch8 (11 versions)
  • every version up to 2.0.4.dfsg.2-7etch9: fixed in 2.0.4.dfsg.2-7etch9
—
xml-security-c1.2.1-3
  • every version up to 1.2.1-3+etch1: fixed in 1.2.1-3+etch1
—
Debian:5.0(2)
PackageVulnerable rangeFix by version rangeDependents
openoffice.org1:2.4.1+dfsg-1 ... 1:2.4.1-17 (6 versions)
  • every version up to 1:2.4.1+dfsg-1+lenny6: fixed in 1:2.4.1+dfsg-1+lenny6
—
xml-security-c1.4.0-3
  • every version up to 1.4.0-3+lenny2: fixed in 1.4.0-3+lenny2
—
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
openoffice.org—
  • every version up to 1:3.1.1-15+squeeze1: fixed in 1:3.1.1-15+squeeze1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.santuario:xmlsec1.4.0, 1.4.1, 1.4.2
  • 1.4.0 up to 1.4.3: fixed in 1.4.3
—

Additional Vendor Advisories

(11)

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 6× in last 7d / 17× 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.

Showing the most recent 100 of 137 total refreshes for this CVE.

  1. 2026-10-09 20:00 UTCEPSS rescore
  2. 2026-10-08 16:33 UTCEPSS rescore
  3. 2026-10-07 23:37 UTCEPSS rescore
  4. 2026-10-06 15:09 UTCEPSS rescore
  5. 2026-10-05 17:37 UTCEPSS rescore
  6. 2026-10-04 23:15 UTCEPSS rescore
  7. 2026-10-03 06:39 UTCOSV refresh
  8. 2026-09-30 14:58 UTCEPSS rescore
  9. 2026-09-29 07:56 UTCEG score recompute
  10. 2026-09-27 13:39 UTCEPSS rescore
  11. 2026-09-26 15:52 UTCEPSS rescore
  12. 2026-09-24 13:57 UTCEPSS rescore
  13. 2026-09-17 19:20 UTCEPSS rescore
  14. 2026-09-15 03:04 UTCEPSS rescore
  15. 2026-09-14 03:20 UTCOSV refresh
  16. 2026-09-12 14:54 UTCEPSS rescore
  17. 2026-09-10 09:24 UTCEPSS rescore
  18. 2026-09-06 13:41 UTCEPSS rescore
  19. 2026-09-05 15:22 UTCEPSS rescore
  20. 2026-09-04 13:55 UTCEPSS rescore
  21. 2026-08-28 21:34 UTCEPSS rescore
  22. 2026-08-27 14:19 UTCEPSS rescore
  23. 2026-08-26 04:40 UTCOSV refresh
  24. 2026-08-25 13:43 UTCEPSS rescore
  25. 2026-08-19 16:58 UTCEPSS rescore
Show 75 more
  1. 2026-08-15 01:24 UTCEPSS rescore
  2. 2026-08-09 21:39 UTCOSV refresh
  3. 2026-08-09 13:41 UTCEPSS rescore
  4. 2026-08-08 16:31 UTCEPSS rescore
  5. 2026-08-06 13:41 UTCEPSS rescore
  6. 2026-08-03 10:28 UTCEPSS rescore
  7. 2026-07-30 16:22 UTCEPSS rescore
  8. 2026-07-30 01:26 UTCEPSS rescore
  9. 2026-07-26 13:37 UTCEG score recompute▲ 5.00
  10. 2026-07-25 14:12 UTCEPSS rescore
  11. 2026-07-24 22:11 UTCOSV refresh
  12. 2026-07-24 14:12 UTCEPSS rescore
  13. 2026-07-23 14:14 UTCEPSS rescore
  14. 2026-07-23 00:58 UTCEG score recompute
  15. 2026-07-23 00:36 UTCEG score recompute
  16. 2026-07-23 00:03 UTCEG score recompute
  17. 2026-07-22 21:42 UTCEG score recompute
  18. 2026-07-22 14:03 UTCEPSS rescore
  19. 2026-07-21 15:20 UTCEPSS rescore
  20. 2026-07-20 17:03 UTCEPSS rescore
  21. 2026-07-20 17:03 UTCEPSS rescore
  22. 2026-07-18 09:59 UTCEPSS rescore
  23. 2026-07-16 16:58 UTCEPSS rescore
  24. 2026-07-15 16:54 UTCEPSS rescore
  25. 2026-07-15 16:54 UTCEPSS rescore
  26. 2026-07-15 01:55 UTCEPSS rescore
  27. 2026-07-13 22:25 UTCEPSS rescore
  28. 2026-07-13 06:07 UTCEPSS rescore
  29. 2026-07-11 08:22 UTCEPSS rescore
  30. 2026-07-11 08:22 UTCEPSS rescore
  31. 2026-07-09 19:04 UTCEPSS rescore
  32. 2026-07-08 15:10 UTCEPSS rescore
  33. 2026-07-07 17:12 UTCOSV refresh
  34. 2026-07-06 16:23 UTCEPSS rescore
  35. 2026-07-06 02:19 UTCEPSS rescore
  36. 2026-07-06 02:19 UTCEPSS rescore
  37. 2026-07-05 02:26 UTCEPSS rescore
  38. 2026-07-05 02:26 UTCEPSS rescore
  39. 2026-07-04 06:27 UTCEPSS rescore
  40. 2026-07-01 15:02 UTCEPSS rescore
  41. 2026-06-30 23:19 UTCEPSS rescore
  42. 2026-06-29 14:02 UTCEPSS rescore
  43. 2026-06-29 14:02 UTCEPSS rescore
  44. 2026-06-28 04:52 UTCEPSS rescore
  45. 2026-06-28 04:52 UTCEPSS rescore
  46. 2026-06-27 03:05 UTCEPSS rescore
  47. 2026-06-25 13:46 UTCEPSS rescore
  48. 2026-06-25 13:46 UTCEPSS rescore
  49. 2026-06-24 14:02 UTCEPSS rescore
  50. 2026-06-24 14:02 UTCEPSS rescore
  51. 2026-06-23 21:29 UTCEPSS rescore
  52. 2026-06-23 21:29 UTCEPSS rescore
  53. 2026-06-22 14:22 UTCEPSS rescore
  54. 2026-06-22 14:22 UTCEPSS rescore
  55. 2026-06-21 14:53 UTCEPSS rescore
  56. 2026-06-19 19:22 UTCEPSS rescore
  57. 2026-06-19 19:22 UTCEPSS rescore
  58. 2026-06-19 04:43 UTCOSV refresh
  59. 2026-06-18 17:49 UTCEPSS rescore
  60. 2026-06-18 17:49 UTCEPSS rescore
  61. 2026-06-17 17:49 UTCEPSS rescore
  62. 2026-06-17 17:49 UTCEPSS rescore
  63. 2026-06-16 17:49 UTCEPSS rescore
  64. 2026-06-16 17:49 UTCEPSS rescore
  65. 2026-06-15 17:44 UTCEPSS rescore
  66. 2026-06-14 23:14 UTCEPSS rescore
  67. 2026-06-14 23:14 UTCEPSS rescore
  68. 2026-06-13 22:57 UTCEPSS rescore
  69. 2026-06-12 23:08 UTCEPSS rescore
  70. 2026-06-12 23:08 UTCEPSS rescore
  71. 2026-06-10 22:14 UTCEPSS rescore
  72. 2026-06-10 13:17 UTCEPSS rescore
  73. 2026-06-08 14:13 UTCEPSS rescore
  74. 2026-06-07 15:22 UTCEPSS rescore
  75. 2026-06-07 15:22 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2009-0217?
CVE-2009-0217 is a medium vulnerability published on July 14, 2009. The design of the W3C XML Signature Syntax and Processing (XMLDsig) recommendation, as implemented in products including (1) the Oracle Security Developer Tools component in Oracle Application Server 10.1.2.3, 10.1.3.4, and 10.1.4.3IM; (2) the WebLogic Server component in BEA Product Suite 10.3,…
When was CVE-2009-0217 disclosed?
CVE-2009-0217 was first published on July 14, 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-0217 actively exploited?
CVE-2009-0217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.4% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
How do I remediate CVE-2009-0217?
A fix for CVE-2009-0217 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2009-0217 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2009-0217

Explore →

Is Your Infrastructure Affected by CVE-2009-0217?

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

Book a Demo →Browse All CVEs