CVE-2002-0656

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (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:P/I:P/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 89.8% 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
Elevated
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 90%
CISA-KEV: Not listedEPSS PROB: 90%CVSS v2: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Buffer overflows in OpenSSL 0.9.6d and earlier, and 0.9.7-beta2 and earlier, allow remote attackers to execute arbitrary code via (1) a large client master key in SSL2 or (2) a large session ID in SSL3.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5HIGHlow confidence
EG Risk
74
EG Risk 74/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%
Exploitation90% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
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
90%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

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

Exploitation public PoC (EG-KEV: elevated) · 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

August 12, 2002

Last Modified

June 16, 2026

References (24)

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2002-08-08redhat
redhatpatch2002-07-31redhat
redhatpatch2002-07-30redhat
redhatpatch2002-07-30redhat

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 rangeFixed inDependents
openssl—0.9.6c-2.woody.1—
openssl0940.9.4-6, 0.9.4-6.potato.30.9.4-6.woody.2—
openssl095—0.9.5a-6.woody.1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssl—0.9.6e-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl—0.9.6e-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl—0.9.6e-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl—0.9.6e-1—

All Vendor Advisories

(4)

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 1× in last 7d / 2× 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-29 02:35 UTCEG score recompute
  2. 2026-09-12 05:23 UTCOSV refresh
  3. 2026-08-24 11:12 UTCOSV refresh
  4. 2026-08-08 07:26 UTCOSV refresh
  5. 2026-07-26 13:22 UTCEG score recompute▲ 7.50
  6. 2026-07-23 00:44 UTCEG score recompute
  7. 2026-07-23 00:30 UTCVendor advisory
  8. 2026-07-23 00:30 UTCGHSA enrichment
  9. 2026-07-23 00:27 UTCVendor advisory
  10. 2026-07-23 00:27 UTCGHSA enrichment
  11. 2026-07-23 00:25 UTCEG score recompute▼ 9.00
  12. 2026-07-22 23:48 UTCEG score recompute
  13. 2026-07-22 21:28 UTCEG score recompute
  14. 2026-07-20 17:02 UTCEPSS rescore
  15. 2026-07-18 09:59 UTCEPSS rescore
  16. 2026-07-15 16:53 UTCEPSS rescore
  17. 2026-07-09 13:45 UTCOSV refresh
  18. 2026-07-02 14:00 UTCEPSS rescore
  19. 2026-06-27 03:04 UTCEPSS rescore
  20. 2026-06-24 14:01 UTCEPSS rescore
  21. 2026-06-23 21:29 UTCEPSS rescore
  22. 2026-06-21 02:15 UTCOSV refresh
  23. 2026-06-17 17:49 UTCEPSS rescore
  24. 2026-06-12 23:07 UTCEPSS rescore
  25. 2026-06-11 13:55 UTCEPSS rescore
Show 24 more
  1. 2026-06-10 22:13 UTCEPSS rescore
  2. 2026-06-10 13:17 UTCEPSS rescore
  3. 2026-06-02 20:10 UTCEPSS rescore
  4. 2026-06-01 13:48 UTCEPSS rescore
  5. 2026-05-31 19:11 UTCEG score recompute
  6. 2026-05-31 19:11 UTCVendor advisory
  7. 2026-05-31 19:11 UTCGHSA enrichment
  8. 2026-05-29 13:40 UTCEPSS rescore
  9. 2026-05-28 13:42 UTCEPSS rescore
  10. 2026-05-28 13:42 UTCEPSS rescore
  11. 2026-05-28 13:42 UTCEPSS rescore
  12. 2026-05-28 13:42 UTCEPSS rescore
  13. 2026-05-27 13:37 UTCEPSS rescore
  14. 2026-05-27 13:37 UTCEPSS rescore
  15. 2026-05-26 13:41 UTCEPSS rescore
  16. 2026-05-26 13:41 UTCEPSS rescore
  17. 2026-05-26 13:41 UTCEPSS rescore
  18. 2026-05-26 07:16 UTCEPSS rescore
  19. 2026-05-26 07:16 UTCEPSS rescore
  20. 2026-05-22 08:52 UTCOSV refresh
  21. 2026-05-21 22:38 UTCEPSS rescore
  22. 2026-05-20 22:36 UTCEPSS rescore
  23. 2026-05-18 21:29 UTCEPSS rescore
  24. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-40347
    First seen Sep 17, 2002

    Apache mod_ssl OpenSSL < 0.9.6d / < 0.9.7-beta2 - 'openssl-too-open.c' SSL2 KEY_ARG Overflow

    Open source ↗

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2002-0656?
CVE-2002-0656 is a high vulnerability published on August 12, 2002. Buffer overflows in OpenSSL 0.9.6d and earlier, and 0.9.7-beta2 and earlier, allow remote attackers to execute arbitrary code via (1) a large client master key in SSL2 or (2) a large session ID in SSL3.
When was CVE-2002-0656 disclosed?
CVE-2002-0656 was first published on August 12, 2002, 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-2002-0656 actively exploited?
CVE-2002-0656 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2002-0656?
A fix for CVE-2002-0656 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-2002-0656

Explore →

Is Your Infrastructure Affected by CVE-2002-0656?

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

Book a Demo →Browse All CVEs