CVE-2008-0960

HIGHCVSS v2 · 10.010.0
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. 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 69% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Weaponized
10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 69%
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 69%CVSS v2: 10.0Exploit: Exploit-DB (verified)Exposed services: Not assessed

A fix is available — apply it.

SNMPv3 HMAC verification in (1) Net-SNMP 5.2.x before 5.2.4.1, 5.3.x before 5.3.2.1, and 5.4.x before 5.4.1.1; (2) UCD-SNMP; (3) eCos; (4) Juniper Session and Resource Control (SRC) C-series 1.0.0 through 2.0.0; (5) NetApp (aka Network Appliance) Data ONTAP 7.3RC1 and 7.3RC2; (6) SNMP Research before 16.2; (7) multiple Cisco IOS, CatOS, ACE, and Nexus products; (8) Ingate Firewall 3.1.0 and later and SIParator 3.1.0 and later; (9) HP OpenView SNMP Emanate Master Agent 15.x; and possibly other products relies on the client to specify the HMAC length, which makes it easier for remote attackers to bypass SNMP authentication via a length value of 1, which only checks the first byte.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0HIGHlow confidence
EG Risk
77
EG Risk 77/100

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 (value × EchelonGraph’s weight)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation69% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
69%
EPSS %ILE
99th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track 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: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

June 10, 2008

Last Modified

April 23, 2026

References (64)

15 of 64 shown · show the other 49

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibsnmp10 (5.3.1-6ubuntu2.2) @ gutsy2026-05-30ubuntu
redhatucd-snmp-0:4.2.5-8.AS21.72008-06-10redhat
redhatnet-snmp-1:5.3.1-24.el5_2.12008-06-10redhat

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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
net-snmp—
  • every version up to 5.4.1~dfsg-8.1: fixed in 5.4.1~dfsg-8.1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
net-snmp—
  • every version up to 5.4.1~dfsg-8.1: fixed in 5.4.1~dfsg-8.1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
net-snmp—
  • every version up to 5.4.1~dfsg-8.1: fixed in 5.4.1~dfsg-8.1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
net-snmp—
  • every version up to 5.4.1~dfsg-8.1: fixed in 5.4.1~dfsg-8.1
—
Debian:4.0(1)
PackageVulnerable rangeFix by version rangeDependents
net-snmp5.2.3-7, 5.2.3-7etch1, 5.2.3-7etch2, 5.2.3-7etch3
  • every version up to 5.2.3-7etch4: fixed in 5.2.3-7etch4
—
Debian:5.0(1)
PackageVulnerable rangeFix by version rangeDependents
net-snmp—
  • every version up to 5.4.1~dfsg-7.1+lenny1: fixed in 5.4.1~dfsg-7.1+lenny1
—

Weakness Classification(1)

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

All Vendor Advisories

(3)

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 4× in last 7d / 12× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 73 of 83 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 27 repeat rows among the latest 100 are merged into the row they repeat. The 10 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-10 19:53 UTCEPSS rescoreEPSS 69% · 99th percentile
  2. 2026-10-09 20:00 UTCEPSS rescoreEPSS 69% · 99th percentile
  3. 2026-10-07 23:37 UTCEPSS rescoreEPSS 69% · 99th percentile
  4. 2026-10-06 15:09 UTCEPSS rescoreEPSS 69% · 99th percentile
  5. 2026-10-04 03:08 UTCOSV refresh
  6. 2026-10-03 14:20 UTCEPSS rescoreEPSS 69% · 99th percentile
  7. 2026-09-30 14:57 UTCEPSS rescoreEPSS 69% · 99th percentile
  8. 2026-09-29 07:47 UTCEG score recompute
  9. 2026-09-18 19:20 UTCEPSS rescoreEPSS 69% · 99th percentile
  10. 2026-09-17 19:20 UTCEPSS rescoreEPSS 69% · 99th percentile
  11. 2026-09-14 17:44 UTCOSV refresh
  12. 2026-09-12 14:54 UTCEPSS rescoreEPSS 69% · 99th percentile
  13. 2026-09-05 15:22 UTCEPSS rescoreEPSS 69% · 99th percentile
  14. 2026-09-04 13:55 UTCEPSS rescoreEPSS 69% · 99th percentile
  15. 2026-09-04 04:59 UTCEPSS rescoreEPSS 69% · 99th percentile
  16. 2026-08-26 17:16 UTCOSV refresh
  17. 2026-08-10 07:10 UTCOSV refresh
  18. 2026-08-08 16:30 UTCEPSS rescoreEPSS 69% · 99th percentile
  19. 2026-08-07 16:20 UTCEPSS rescoreEPSS 69% · 99th percentile
  20. 2026-08-06 13:41 UTCEPSS rescoreEPSS 69% · 99th percentile
  21. 2026-08-05 19:11 UTCEPSS rescoreEPSS 69% · 99th percentile
  22. 2026-08-04 15:03 UTCEPSS rescoreEPSS 69% · 99th percentile
  23. 2026-07-30 16:22 UTCEPSS rescoreEPSS 69% · 99th percentile
  24. 2026-07-28 15:30 UTCEPSS rescoreEPSS 69% · 99th percentile
  25. 2026-07-26 13:34 UTCEG score recomputeAssessed again: 10.0 HIGH
Show 48 more
  1. 2026-07-25 07:41 UTCOSV refresh
  2. 2026-07-24 14:11 UTCEPSS rescoreEPSS 69% · 99th percentile
  3. 2026-07-23 00:55 UTCEG score recompute
  4. 2026-07-23 00:34 UTCEG score recompute▼ 6.30
  5. 2026-07-23 00:00 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
  6. 2026-07-22 21:39 UTCEG score recompute
  7. 2026-07-22 14:03 UTCEPSS rescoreEPSS 69% · 99th percentile
  8. 2026-07-20 17:03 UTCEPSS rescoreEPSS 69% · 99th percentile
  9. 2026-07-16 16:58 UTCEPSS rescoreEPSS 69% · 99th percentile
  10. 2026-07-15 16:54 UTCEPSS rescoreEPSS 69% · 99th percentile
  11. 2026-07-08 02:27 UTCOSV refresh
  12. 2026-07-05 02:26 UTCEPSS rescoreEPSS 69% · 99th percentile
  13. 2026-07-04 06:27 UTCEPSS rescoreEPSS 69% · 99th percentile
  14. 2026-07-01 15:02 UTCEPSS rescoreEPSS 69% · 99th percentile
  15. 2026-06-27 03:04 UTCEPSS rescoreEPSS 69% · 99th percentile
  16. 2026-06-25 13:46 UTCEPSS rescoreEPSS 69% · 99th percentile
  17. 2026-06-24 14:02 UTCEPSS rescoreEPSS 69% · 99th percentile
  18. 2026-06-23 21:29 UTCEPSS rescoreEPSS 69% · 99th percentile
  19. 2026-06-21 01:56 UTCEPSS rescoreEPSS 69% · 99th percentile
  20. 2026-06-19 19:22 UTCEPSS rescoreEPSS 69% · 99th percentile
  21. 2026-06-19 14:25 UTCOSV refresh
  22. 2026-06-18 17:49 UTCEPSS rescoreEPSS 69% · 99th percentile
  23. 2026-06-17 17:49 UTCEPSS rescoreEPSS 69% · 99th percentile
  24. 2026-06-16 17:49 UTCEPSS rescoreEPSS 69% · 99th percentile
  25. 2026-06-15 17:44 UTCEPSS rescoreEPSS 69% · 99th percentile
  26. 2026-06-13 22:57 UTCEPSS rescoreEPSS 23% · 96th percentile
  27. 2026-06-12 23:08 UTCEPSS rescoreEPSS 23% · 96th percentile
  28. 2026-06-10 22:14 UTCEPSS rescoreEPSS 23% · 96th percentile
  29. 2026-06-10 13:17 UTCEPSS rescoreEPSS 23% · 96th percentile
  30. 2026-06-07 15:21 UTCEPSS rescoreEPSS 23% · 96th percentile
  31. 2026-06-06 13:44 UTCEPSS rescoreEPSS 23% · 96th percentile
  32. 2026-06-05 22:44 UTCEPSS rescoreEPSS 23% · 96th percentile
  33. 2026-06-05 06:07 UTCEPSS rescoreEPSS 23% · 96th percentile
  34. 2026-06-04 13:09 UTCEPSS rescoreEPSS 23% · 96th percentile
  35. 2026-06-02 20:10 UTCEPSS rescoreEPSS 23% · 96th percentile
  36. 2026-06-01 13:49 UTCEPSS rescoreEPSS 23% · 96th percentile
  37. 2026-05-31 22:28 UTCEPSS rescoreEPSS 23% · 96th percentile
  38. 2026-05-31 00:13 UTCEPSS rescoreEPSS 23% · 96th percentile
  39. 2026-05-30 21:28 UTCEG score recompute
  40. 2026-05-30 21:28 UTCVendor advisory
  41. 2026-05-30 21:28 UTCGHSA enrichmentGHSA-xmp9-m365-hwwg · GitHub severity HIGH
  42. 2026-05-30 14:53 UTCOSV refresh
  43. 2026-05-29 13:40 UTCEPSS rescoreEPSS 23% · 96th percentile
  44. 2026-05-28 13:42 UTCEPSS rescoreEPSS 23% · 96th percentile
  45. 2026-05-27 13:37 UTCEPSS rescoreEPSS 23% · 96th percentile
  46. 2026-05-26 13:41 UTCEPSS rescoreEPSS 23% · 96th percentile
  47. 2026-05-26 07:16 UTCEPSS rescoreEPSS 21% · 95th percentile
  48. 2026-05-24 16:42 UTCEPSS rescoreEPSS 21% · 95th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-5790✓ verified
    Published Jun 12, 2008

    SNMPv3 - HMAC Validation error Remote Authentication Bypass

    Open source ↗

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

Same vendor

2 shown

redhat:RHSA-2008:0529 · ubuntu:USN-685-1

Frequently asked(4)

What is CVE-2008-0960?
CVE-2008-0960 is a high-severity vulnerability; its CVE record was published on June 10, 2008. SNMPv3 HMAC verification in (1) Net-SNMP 5.2.x before 5.2.4.1, 5.3.x before 5.3.2.1, and 5.4.x before 5.4.1.1; (2) UCD-SNMP; (3) eCos; (4) Juniper Session and Resource Control (SRC) C-series 1.0.0 through 2.0.0; (5) NetApp (aka Network Appliance) Data ONTAP 7.3RC1 and 7.3RC2; (6) SNMP Research…
When was CVE-2008-0960 made public?
CVE-2008-0960 was made public on June 9, 2008: that is the date its CVE record's CNA, CERT/CC, gives for when the vulnerability was made public. The CVE record itself was published on June 10, 2008. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2008-0960 actively exploited?
CVE-2008-0960 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 69% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2008-0960?
A fix for CVE-2008-0960 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-2008-0960

Explore →

Is Your Infrastructure Affected by CVE-2008-0960?

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

Book a Demo →Browse All CVEs