CVE-2008-5161

LOWNVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2022-05-14. NVD baseline CVSS 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
3.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 15%CVSS: 3.7Exploit: NoneExposed: 0

A fix is available — apply it.

Error handling in the SSH protocol in (1) SSH Tectia Client and Server and Connector 4.0 through 4.4.11, 5.0 through 5.2.4, and 5.3 through 5.3.8; Client and Server and ConnectSecure 6.0 through 6.0.4; Server for Linux on IBM System z 6.0.4; Server for IBM z/OS 5.5.1 and earlier, 6.0.0, and 6.0.1; and Client 4.0-J through 4.3.3-J and 4.0-K through 4.3.10-K; and (2) OpenSSH 4.7p1 and possibly other versions, when using a block cipher algorithm in Cipher Block Chaining (CBC) mode, makes it easier for remote attackers to recover certain plaintext data from an arbitrary block of ciphertext in an SSH session via unknown vectors.

CVSS v3
3.7
EG Score
3.7(medium)
EPSS
96.4%
KEV
Not listed

Published

November 19, 2008

Last Modified

May 28, 2026

References (80)

Vendor Advisories for CVE-2008-5161(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenssh-0:4.3p2-36.el52009-09-02redhat

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.

Weakness Classification(2)

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

All Vendor Advisories

(1)

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

Publicly available exploits

(1 reference)

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

  • Metasploitauxiliary/scanner/ssh/ssh_version✓ verified
    First seen Jan 1, 2008

    SSH Version Scanner

    Open source ↗

Frequently asked(5)

What is CVE-2008-5161?
CVE-2008-5161 is a low vulnerability published on November 19, 2008. Error handling in the SSH protocol in (1) SSH Tectia Client and Server and Connector 4.0 through 4.4.11, 5.0 through 5.2.4, and 5.3 through 5.3.8; Client and Server and ConnectSecure 6.0 through 6.0.4; Server for Linux on IBM System z 6.0.4; Server for IBM z/OS 5.5.1 and earlier, 6.0.0, and 6.0.1;…
When was CVE-2008-5161 disclosed?
CVE-2008-5161 was first published in the National Vulnerability Database on November 19, 2008, with the most recent update on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2008-5161 actively exploited?
CVE-2008-5161 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2008-5161?
CVE-2008-5161 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2008-5161?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2008-5161, 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-2008-5161

Explore →

Is Your Infrastructure Affected by CVE-2008-5161?

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

Start Free Scan →Browse All CVEs