CVE-2009-0130

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory published 2022-05-02. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

lib/crypto/c_src/crypto_drv.c in erlang does not properly check the return value from the OpenSSL DSA_do_verify function, which might allow remote attackers to bypass validation of the certificate chain via a malformed SSL/TLS signature, a similar vulnerability to CVE-2008-5077. NOTE: a package maintainer disputes this issue, reporting that there is a proper check within the only code that uses the applicable part of crypto_drv.c, and thus "this report is invalid.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.2%
EPSS %ILE
67th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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

Published

January 15, 2009

Last Modified

April 23, 2026

Advisory Details (1)

Auto-updated May 30, 2026
No fix on record yet.
generic

oss-security - CVE Request -- tsqllib, slurm-llnl, libnasl, libcrypt-openssl-dsa-perl, erlang, boinc-client, m2crypto

http://openwall.com/lists/oss-security/2009/01/12/4

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:23.2.6+dfsg-1 ... 1:29.0~rc3+dfsg-4 (117 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:25.2.3+dfsg-1 ... 1:29.1.1+dfsg-1 (80 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.1.1+dfsg-1 (41 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
erlang1:27.3.4.1+dfsg-1 ... 1:29.1.1+dfsg-1 (38 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 18× 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 82 of 121 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. 18 repeat rows among the latest 100 are merged into the row they repeat. The 39 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-10 19:54 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  2. 2026-10-09 20:00 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  3. 2026-10-08 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  4. 2026-10-07 23:37 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  5. 2026-10-06 15:09 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  6. 2026-10-05 17:37 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  7. 2026-10-04 23:15 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  8. 2026-10-03 21:58 UTCOSV refresh
  9. 2026-09-30 14:58 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  10. 2026-09-29 07:56 UTCEG score recompute
  11. 2026-09-27 13:39 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  12. 2026-09-26 15:52 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  13. 2026-09-24 13:57 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  14. 2026-09-17 19:20 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  15. 2026-09-15 03:04 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  16. 2026-09-14 12:14 UTCOSV refresh
  17. 2026-09-13 16:40 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  18. 2026-09-12 14:54 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  19. 2026-09-10 09:24 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  20. 2026-09-06 13:41 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  21. 2026-09-05 15:22 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  22. 2026-09-04 13:55 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  23. 2026-08-28 21:34 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  24. 2026-08-27 14:19 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  25. 2026-08-26 13:13 UTCOSV refresh
Show 57 more
  1. 2026-08-25 13:43 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  2. 2026-08-19 16:58 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  3. 2026-08-15 01:24 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  4. 2026-08-10 02:09 UTCOSV refresh
  5. 2026-08-09 13:41 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  6. 2026-08-08 16:31 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  7. 2026-08-06 13:41 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  8. 2026-08-03 10:28 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  9. 2026-07-30 16:22 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  10. 2026-07-30 01:26 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  11. 2026-07-25 14:12 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  12. 2026-07-25 02:41 UTCOSV refresh
  13. 2026-07-23 14:14 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  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 rescoreEPSS 1.2% · 65th percentile
  19. 2026-07-21 15:20 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  20. 2026-07-20 17:03 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  21. 2026-07-18 09:59 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  22. 2026-07-16 16:58 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  23. 2026-07-15 16:54 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  24. 2026-07-15 01:55 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  25. 2026-07-13 22:25 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  26. 2026-07-11 08:22 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  27. 2026-07-09 19:04 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  28. 2026-07-08 15:10 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  29. 2026-07-07 21:12 UTCOSV refresh
  30. 2026-07-06 16:23 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  31. 2026-07-06 02:19 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  32. 2026-07-05 02:26 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  33. 2026-07-04 06:27 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  34. 2026-07-01 15:02 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  35. 2026-06-30 23:19 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  36. 2026-06-29 14:02 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  37. 2026-06-28 14:03 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  38. 2026-06-28 04:52 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  39. 2026-06-27 03:05 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  40. 2026-06-25 13:46 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  41. 2026-06-24 14:02 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  42. 2026-06-23 21:29 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  43. 2026-06-22 14:22 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  44. 2026-06-21 14:53 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  45. 2026-06-21 01:56 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  46. 2026-06-19 19:22 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  47. 2026-06-19 08:55 UTCOSV refresh
  48. 2026-06-18 17:49 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  49. 2026-06-17 17:49 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  50. 2026-06-16 17:49 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  51. 2026-06-15 17:44 UTCEPSS rescoreEPSS 1.2% · 64th percentile
  52. 2026-06-14 23:14 UTCEPSS rescoreEPSS <0.1% · 18th percentile
  53. 2026-06-13 22:57 UTCEPSS rescoreEPSS <0.1% · 18th percentile
  54. 2026-06-12 23:08 UTCEPSS rescoreEPSS <0.1% · 18th percentile
  55. 2026-06-10 22:14 UTCEPSS rescoreEPSS <0.1% · 17th percentile
  56. 2026-06-10 13:17 UTCEPSS rescoreEPSS <0.1% · 17th percentile
  57. 2026-06-08 14:13 UTCEPSS rescoreEPSS <0.1% · 17th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2009-0130?
CVE-2009-0130 is a high vulnerability published on January 15, 2009. lib/crypto/csrc/cryptodrv.c in erlang does not properly check the return value from the OpenSSL DSAdoverify function, which might allow remote attackers to bypass validation of the certificate chain via a malformed SSL/TLS signature, a similar vulnerability to CVE-2008-5077. NOTE: a package…
When was the CVE record for CVE-2009-0130 published?
The CVE record for CVE-2009-0130 was published on January 15, 2009. That is the record's publication date; the vulnerability itself may have been made public earlier. 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-0130 actively exploited?
CVE-2009-0130 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2009-0130?
CVE-2009-0130 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2009-0130?
No fix for CVE-2009-0130 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2009-0130?

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

Book a Demo →Browse All CVEs