CVE-2002-1359

NONECVSS 0.09.0▲
EchelonGraph scoreLOW confidence

Score elevated to 9.0 because EPSS predicts 87% probability of exploitation within the next 30 days (top 0.5% of all CVEs). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss
Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 80%
CISA-KEV: Not listedEPSS: 80%CVSS: —Exploit: NoneExposed: 0

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

Multiple SSH2 servers and clients do not properly handle large packets or large fields, which may allow remote attackers to cause a denial of service or possibly execute arbitrary code via buffer overflow attacks, as demonstrated by the SSHredder SSH protocol test suite.

CVSS v3
—
EG Score
9.0(low)
EPSS
99.6%
KEV
Not listed

Published

December 23, 2002

Last Modified

June 16, 2026

References (14)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 10× 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-07-11 08:22 UTCEPSS rescore
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-04 06:26 UTCEPSS rescore
  4. 2026-06-27 03:04 UTCEPSS rescore
  5. 2026-06-23 21:29 UTCEPSS rescore
  6. 2026-06-21 14:52 UTCEPSS rescore
  7. 2026-06-21 01:56 UTCEPSS rescore
  8. 2026-06-17 17:49 UTCEPSS rescore
  9. 2026-06-17 17:49 UTCEPSS rescore
  10. 2026-06-15 17:43 UTCEPSS rescore
  11. 2026-06-12 23:08 UTCEPSS rescore
  12. 2026-06-10 22:13 UTCEPSS rescore
  13. 2026-06-06 13:44 UTCEPSS rescore
  14. 2026-06-06 13:44 UTCEPSS rescore
  15. 2026-06-06 13:44 UTCEPSS rescore
  16. 2026-06-05 22:43 UTCEPSS rescore
  17. 2026-06-05 22:43 UTCEPSS rescore
  18. 2026-06-01 13:49 UTCEPSS rescore
  19. 2026-06-01 13:49 UTCEPSS rescore
  20. 2026-05-31 22:28 UTCEPSS rescore
  21. 2026-05-31 18:38 UTCEG score recompute
  22. 2026-05-31 18:38 UTCGHSA enrichment
  23. 2026-05-29 13:40 UTCEPSS rescore
  24. 2026-05-29 13:40 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
Show 8 more
  1. 2026-05-28 13:42 UTCEPSS rescore
  2. 2026-05-28 13:42 UTCEPSS rescore
  3. 2026-05-27 13:37 UTCEPSS rescore
  4. 2026-05-26 07:16 UTCEPSS rescore
  5. 2026-05-26 07:16 UTCEPSS rescore
  6. 2026-05-22 21:15 UTCEPSS rescore
  7. 2026-05-18 21:29 UTCEPSS rescore
  8. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(3 references)

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

  • Exploit-DBEDB-16463✓ verified
    First seen Jun 15, 2010

    PuTTy.exe 0.53 - Remote Buffer Overflow (Metasploit)

    Open source ↗
  • Exploit-DBEDB-1788✓ verified
    First seen May 15, 2006

    PuTTy.exe 0.53 - Validation Remote Buffer Overflow (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/ssh/putty_msg_debug✓ verified
    First seen Dec 16, 2002

    PuTTY Buffer Overflow

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2002-1359?
CVE-2002-1359 is a none vulnerability published on December 23, 2002. Multiple SSH2 servers and clients do not properly handle large packets or large fields, which may allow remote attackers to cause a denial of service or possibly execute arbitrary code via buffer overflow attacks, as demonstrated by the SSHredder SSH protocol test suite.
When was CVE-2002-1359 disclosed?
CVE-2002-1359 was first published in the National Vulnerability Database on December 23, 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-1359 actively exploited?
CVE-2002-1359 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2002-1359?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2002-1359, 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

Explore the affected products and dependency analysis for CVE-2002-1359

Explore →

Is Your Infrastructure Affected by CVE-2002-1359?

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

Start Free Scan →Browse All CVEs