CVE-2004-0079

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 9.5% (95th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 9.5%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

The do_change_cipher_spec function in OpenSSL 0.9.6c to 0.9.6k, and 0.9.7a to 0.9.7c, allows remote attackers to cause a denial of service (crash) via a crafted SSL/TLS handshake that triggers a null dereference.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; 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
9.5%
EPSS %ILE
95th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; 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 (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

November 23, 2004

Last Modified

June 16, 2026

Advisory Details (2)

Auto-updated May 31, 2026
Patch available.
generic

'New OpenSSL releases fix denial of service attacks [17 March 2004]' - MARC

http://marc.info/?l=bugtraq&m=107953412903636&w=2
generic

FedoraNEWS.ORG

http://fedoranews.org/updates/FEDORA-2004-095.shtml

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenssl096b-0:0.9.6b-22.422005-11-02redhat
redhatpatch2005-11-02redhat
redhatopenssl096b-0:0.9.6b-162004-03-17redhat
redhatpatch2004-03-17redhat
redhatpatch2004-03-17redhat

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 5 ecosystems)
Debian:3.0(3)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.6c-2.woody.6: fixed in 0.9.6c-2.woody.6
—
openssl0940.9.4-6, 0.9.4-6.potato.3, 0.9.4-6.woody.3
  • every version up to 0.9.4-6.woody.4: fixed in 0.9.4-6.woody.4
—
openssl0950.9.5a-6.woody.3
  • every version up to 0.9.5a-6.woody.5: fixed in 0.9.5a-6.woody.5
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.7d-1: fixed in 0.9.7d-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.7d-1: fixed in 0.9.7d-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.7d-1: fixed in 0.9.7d-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 0.9.7d-1: fixed in 0.9.7d-1
—

Weakness Classification(1)

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

All Vendor Advisories

(5)

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

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

Frequently asked(5)

What is CVE-2004-0079?
CVE-2004-0079 is a high vulnerability published on November 23, 2004. The dochangecipher_spec function in OpenSSL 0.9.6c to 0.9.6k, and 0.9.7a to 0.9.7c, allows remote attackers to cause a denial of service (crash) via a crafted SSL/TLS handshake that triggers a null dereference.
When was CVE-2004-0079 disclosed?
CVE-2004-0079 was first published on November 23, 2004, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2004-0079 actively exploited?
CVE-2004-0079 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.5% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2004-0079?
CVE-2004-0079 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2004-0079?
A fix for CVE-2004-0079 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2004-0079

Explore →

Is Your Infrastructure Affected by CVE-2004-0079?

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

Book a Demo →Browse All CVEs