CVE-2005-2969

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 4.9% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

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: 5%CVSS v2: 5.0Exploit: None knownExposed: 0

A fix is available — apply it.

The SSL/TLS server implementation in OpenSSL 0.9.7 before 0.9.7h and 0.9.8 before 0.9.8a, when using the SSL_OP_MSIE_SSLV2_RSA_PADDING option, disables a verification step that is required for preventing protocol version rollback attacks, which allows remote attackers to force a client and server to use a weaker protocol than needed via a man-in-the-middle attack.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0(low)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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%
Exploitation5% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
5%
EPSS %ILE
92%
KEV
Not listed

Published

October 18, 2005

Last Modified

April 16, 2026

References (148)

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibssl0.9.7 () @ warty2026-05-31ubuntu
redhatrhn_solaris_bootstrap_5_1_1_3-0:1-02008-08-13redhat
redhatrhn_solaris_bootstrap_5_0_2_3-0:1-02008-06-30redhat
redhatpatch2005-12-19redhat
redhatopenssl096b-0:0.9.6b-22.42005-10-11redhat

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

(9 across 6 ecosystems)
Debian:3.0(3)
PackageVulnerable rangeFixed inDependents
openssl0.9.6c-2.woody.70.9.6c-2.woody.8—
openssl0940.9.4-6, 0.9.4-6.potato.3, 0.9.4-6.woody.30.9.4-6.woody.4—
openssl0950.9.5a-6.woody.3, 0.9.5a-6.woody.50.9.5a-6.woody.6—
Debian:3.1(2)
PackageVulnerable rangeFixed inDependents
openssl0.9.7e-30.9.7e-3sarge1—
openssl0960.9.6m-10.9.6m-1sarge1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssl—0.9.8-3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl—0.9.8-3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl—0.9.8-3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl—0.9.8-3—

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 2× in last 7d / 3× 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-09-10 09:23 UTCEPSS rescore
  2. 2026-09-04 04:59 UTCEPSS rescore
  3. 2026-08-27 19:17 UTCOSV refresh
  4. 2026-08-11 08:31 UTCOSV refresh
  5. 2026-08-08 16:30 UTCEPSS rescore
  6. 2026-08-05 19:11 UTCEPSS rescore
  7. 2026-07-26 13:27 UTCEG score recompute▲ 5.00
  8. 2026-07-26 09:12 UTCOSV refresh
  9. 2026-07-25 14:11 UTCEPSS rescore
  10. 2026-07-24 14:11 UTCEPSS rescore
  11. 2026-07-23 00:48 UTCEG score recompute
  12. 2026-07-23 00:28 UTCEG score recompute
  13. 2026-07-22 23:52 UTCEG score recompute
  14. 2026-07-22 21:32 UTCEG score recompute
  15. 2026-07-18 09:59 UTCEPSS rescore
  16. 2026-07-18 09:59 UTCEPSS rescore
  17. 2026-07-15 16:53 UTCEPSS rescore
  18. 2026-07-15 01:55 UTCEPSS rescore
  19. 2026-07-15 01:55 UTCEPSS rescore
  20. 2026-07-13 22:24 UTCEPSS rescore
  21. 2026-07-13 06:07 UTCEPSS rescore
  22. 2026-07-13 06:07 UTCEPSS rescore
  23. 2026-07-11 08:22 UTCEPSS rescore
  24. 2026-07-11 08:22 UTCEPSS rescore
  25. 2026-07-09 03:09 UTCOSV refresh
Show 65 more
  1. 2026-07-08 15:09 UTCEPSS rescore
  2. 2026-07-06 02:19 UTCEPSS rescore
  3. 2026-07-06 02:19 UTCEPSS rescore
  4. 2026-07-02 14:00 UTCEPSS rescore
  5. 2026-07-01 15:01 UTCEPSS rescore
  6. 2026-06-29 14:02 UTCEPSS rescore
  7. 2026-06-29 14:02 UTCEPSS rescore
  8. 2026-06-28 04:52 UTCEPSS rescore
  9. 2026-06-27 03:04 UTCEPSS rescore
  10. 2026-06-25 13:46 UTCEPSS rescore
  11. 2026-06-24 14:01 UTCEPSS rescore
  12. 2026-06-23 21:29 UTCEPSS rescore
  13. 2026-06-22 14:22 UTCEPSS rescore
  14. 2026-06-22 14:22 UTCEPSS rescore
  15. 2026-06-21 01:56 UTCEPSS rescore
  16. 2026-06-20 15:42 UTCOSV refresh
  17. 2026-06-19 19:22 UTCEPSS rescore
  18. 2026-06-18 17:49 UTCEPSS rescore
  19. 2026-06-18 17:49 UTCEPSS rescore
  20. 2026-06-17 17:49 UTCEPSS rescore
  21. 2026-06-17 17:49 UTCEPSS rescore
  22. 2026-06-16 17:49 UTCEPSS rescore
  23. 2026-06-16 17:49 UTCEPSS rescore
  24. 2026-06-15 17:44 UTCEPSS rescore
  25. 2026-06-13 22:56 UTCEPSS rescore
  26. 2026-06-12 23:08 UTCEPSS rescore
  27. 2026-06-11 13:55 UTCEPSS rescore
  28. 2026-06-10 22:14 UTCEPSS rescore
  29. 2026-06-10 13:17 UTCEPSS rescore
  30. 2026-06-08 14:13 UTCEPSS rescore
  31. 2026-06-07 15:21 UTCEPSS rescore
  32. 2026-06-06 13:44 UTCEPSS rescore
  33. 2026-06-06 13:44 UTCEPSS rescore
  34. 2026-06-05 22:43 UTCEPSS rescore
  35. 2026-06-05 22:43 UTCEPSS rescore
  36. 2026-06-05 06:07 UTCEPSS rescore
  37. 2026-06-05 06:07 UTCEPSS rescore
  38. 2026-06-04 13:09 UTCEPSS rescore
  39. 2026-06-04 13:09 UTCEPSS rescore
  40. 2026-06-02 20:10 UTCEPSS rescore
  41. 2026-06-02 20:10 UTCEPSS rescore
  42. 2026-06-01 13:49 UTCEPSS rescore
  43. 2026-06-01 13:49 UTCEPSS rescore
  44. 2026-05-31 22:28 UTCEPSS rescore
  45. 2026-05-31 11:56 UTCEG score recompute
  46. 2026-05-31 11:56 UTCVendor advisory
  47. 2026-05-31 11:56 UTCGHSA enrichment
  48. 2026-05-31 00:13 UTCEPSS rescore
  49. 2026-05-31 00:13 UTCEPSS rescore
  50. 2026-05-29 13:40 UTCEPSS rescore
  51. 2026-05-29 13:40 UTCEPSS rescore
  52. 2026-05-28 13:42 UTCEPSS rescore
  53. 2026-05-28 13:42 UTCEPSS rescore
  54. 2026-05-28 13:42 UTCEPSS rescore
  55. 2026-05-28 03:03 UTCOSV refresh
  56. 2026-05-27 13:37 UTCEPSS rescore
  57. 2026-05-26 13:41 UTCEPSS rescore
  58. 2026-05-26 13:41 UTCEPSS rescore
  59. 2026-05-24 16:42 UTCEPSS rescore
  60. 2026-05-21 22:38 UTCEPSS rescore
  61. 2026-05-20 22:36 UTCEPSS rescore
  62. 2026-05-20 22:36 UTCEPSS rescore
  63. 2026-05-20 11:20 UTCEPSS rescore
  64. 2026-05-20 11:20 UTCEPSS rescore
  65. 2026-05-18 21:29 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2005-2969?
CVE-2005-2969 is a medium vulnerability published on October 18, 2005. The SSL/TLS server implementation in OpenSSL 0.9.7 before 0.9.7h and 0.9.8 before 0.9.8a, when using the SSLOPMSIESSLV2RSA_PADDING option, disables a verification step that is required for preventing protocol version rollback attacks, which allows remote attackers to force a client and server to…
When was CVE-2005-2969 disclosed?
CVE-2005-2969 was first published in the National Vulnerability Database on October 18, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-2969 actively exploited?
CVE-2005-2969 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5% probability of exploitation in the next 30 days, which ranks it in the top 8.5% of all scored CVEs.
How do I remediate CVE-2005-2969?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-2969, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2005-2969

Explore →

Is Your Infrastructure Affected by CVE-2005-2969?

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

Start Free Scan →Browse All CVEs