CVE-2009-0590

MEDIUMCVSS v2 · 5.05.0
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 5.0 — NVD rates that MEDIUM (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:L/Au:N/C:N/I:N/A:P. 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.7% 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
5.0EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 6.7%CVSS v2: 5.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The ASN1_STRING_print_ex function in OpenSSL before 0.9.8k allows remote attackers to cause a denial of service (invalid memory access and application crash) via vectors that trigger printing of a (1) BMPString or (2) UniversalString with an invalid encoded length.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0MEDIUMlow confidence
EG Risk
25
EG Risk 25/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)
Severity50% × 45%
The EG Score, 5.0 of 10.
Exploitation6.7% × 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or 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.
EPSS PROB
6.7%
EPSS %ILE
93rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or 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

March 27, 2009

Last Modified

April 23, 2026

References (60)

15 of 60 shown · show the other 45

Vendor Advisories for CVE-2009-0590(2)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibssl0.9.8 (0.9.8g-4ubuntu3.5) @ hardy2026-05-30ubuntu
redhatopenssl-0:0.9.7a-43.17.el4_8.52010-03-25redhat
redhatopenssl-0:0.9.8e-12.el52009-09-02redhat

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

(7 across 6 ecosystems)
Debian:4.0(2)
PackageVulnerable rangeFix by version rangeDependents
openssl0.9.8c-4 ... 0.9.8c-4etch4 (6 versions)
  • every version up to 0.9.8c-4etch5: fixed in 0.9.8c-4etch5
—
openssl0970.9.7k-3.1, 0.9.7k-3.1etch1, 0.9.7k-3.1etch2
  • every version up to 0.9.7k-3.1etch3: fixed in 0.9.7k-3.1etch3
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.8g-16: fixed in 0.9.8g-16
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.8g-16: fixed in 0.9.8g-16
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.8g-16: fixed in 0.9.8g-16
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.8g-16: fixed in 0.9.8g-16
—
Debian:5.0(1)
PackageVulnerable rangeFix by version rangeDependents
openssl0.9.8g-15
  • every version up to 0.9.8g-15+lenny1: fixed in 0.9.8g-15+lenny1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 8× in last 7d / 19× 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.

Showing the most recent 83 of 116 refreshes on record for this CVE.

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. 17 repeat rows among the latest 100 are merged into the row they repeat. The 33 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 01:55 UTCEG score recompute
  2. 2026-10-11 13:38 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  4. 2026-10-09 20:00 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  5. 2026-10-08 16:33 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  6. 2026-10-07 23:37 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  7. 2026-10-06 15:09 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  8. 2026-10-05 17:37 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  9. 2026-10-03 17:19 UTCOSV refresh
  10. 2026-09-30 14:58 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  11. 2026-09-29 07:57 UTCEG score recompute
  12. 2026-09-27 13:39 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  13. 2026-09-26 15:52 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  14. 2026-09-24 13:57 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  15. 2026-09-17 19:20 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  16. 2026-09-15 03:04 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  17. 2026-09-14 07:50 UTCOSV refresh
  18. 2026-09-13 16:40 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  19. 2026-09-12 14:54 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  20. 2026-09-10 09:24 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  21. 2026-09-06 13:41 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  22. 2026-09-05 15:22 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  23. 2026-09-04 13:55 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  24. 2026-08-28 21:34 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  25. 2026-08-27 14:19 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
Show 58 more
  1. 2026-08-26 09:13 UTCOSV refresh
  2. 2026-08-25 13:43 UTCEPSS rescoreEPSS 6.7% · 93rd percentile
  3. 2026-08-19 16:58 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  4. 2026-08-15 01:24 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  5. 2026-08-09 23:39 UTCOSV refresh
  6. 2026-08-09 13:41 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  7. 2026-08-08 16:31 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  8. 2026-08-06 13:41 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  9. 2026-08-03 10:28 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  10. 2026-07-30 16:22 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  11. 2026-07-30 01:26 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  12. 2026-07-26 13:37 UTCEG score recomputeFirst assessed: 5.0 MEDIUM
  13. 2026-07-25 14:12 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  14. 2026-07-25 00:11 UTCOSV refresh
  15. 2026-07-24 14:12 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  16. 2026-07-23 14:14 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  17. 2026-07-23 00:58 UTCEG score recompute
  18. 2026-07-23 00:36 UTCEG score recompute
  19. 2026-07-23 00:03 UTCEG score recompute
  20. 2026-07-22 21:42 UTCEG score recompute
  21. 2026-07-22 14:03 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  22. 2026-07-21 15:20 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  23. 2026-07-20 17:03 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  24. 2026-07-18 09:59 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  25. 2026-07-16 16:58 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  26. 2026-07-15 16:54 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  27. 2026-07-15 01:55 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  28. 2026-07-13 22:25 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  29. 2026-07-11 08:22 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  30. 2026-07-09 19:04 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  31. 2026-07-08 15:10 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  32. 2026-07-07 19:41 UTCOSV refresh
  33. 2026-07-06 16:23 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  34. 2026-07-06 02:19 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  35. 2026-07-05 02:26 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  36. 2026-07-04 06:27 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  37. 2026-07-01 15:02 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  38. 2026-06-30 23:19 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  39. 2026-06-28 04:52 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  40. 2026-06-27 03:05 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  41. 2026-06-25 13:46 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  42. 2026-06-24 14:02 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  43. 2026-06-23 21:29 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  44. 2026-06-22 14:22 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  45. 2026-06-21 14:53 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  46. 2026-06-21 01:56 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  47. 2026-06-19 19:22 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  48. 2026-06-19 06:55 UTCOSV refresh
  49. 2026-06-18 17:49 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  50. 2026-06-17 17:49 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  51. 2026-06-16 17:49 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  52. 2026-06-15 17:44 UTCEPSS rescoreEPSS 6.2% · 92nd percentile
  53. 2026-06-14 23:14 UTCEPSS rescoreEPSS 10% · 93rd percentile
  54. 2026-06-13 22:57 UTCEPSS rescoreEPSS 10% · 93rd percentile
  55. 2026-06-12 23:08 UTCEPSS rescoreEPSS 10% · 93rd percentile
  56. 2026-06-10 22:14 UTCEPSS rescoreEPSS 10% · 93rd percentile
  57. 2026-06-10 13:17 UTCEPSS rescoreEPSS 10% · 93rd percentile
  58. 2026-06-08 14:13 UTCEPSS rescoreEPSS 10% · 93rd percentile

Related CVEs(same product + same vendor + same CWE)

Frequently asked(4)

What is CVE-2009-0590?
CVE-2009-0590 is a medium-severity vulnerability; its CVE record was published on March 27, 2009. The ASN1STRINGprint_ex function in OpenSSL before 0.9.8k allows remote attackers to cause a denial of service (invalid memory access and application crash) via vectors that trigger printing of a (1) BMPString or (2) UniversalString with an invalid encoded length.
When was CVE-2009-0590 made public?
CVE-2009-0590 was made public on March 25, 2009: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on March 27, 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-0590 actively exploited?
CVE-2009-0590 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.7% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
How do I remediate CVE-2009-0590?
A fix for CVE-2009-0590 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2009-0590 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-0590

Explore →

Is Your Infrastructure Affected by CVE-2009-0590?

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

Book a Demo →Browse All CVEs