# CVE-2008-0960: Auth bypass in n/a

> Remote attackers can bypass SNMPv3 authentication by specifying a short HMAC length, allowing unauthorized access to network devices and servers.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-0960, DTSA-137-1, GHSA-xmp9-m365-hwwg, RHSA-2008:0528

## What is CVE-2008-0960?

CVE-2008-0960 is a critical authentication bypass vulnerability in n/a, published on 10 Jun 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2008-0960?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ucd-snmp` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.2.5-8.AS21.7 |
| `ucd-snmp-devel` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.2.5-8.AS21.7 |
| `ucd-snmp-utils` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.2.5-8.AS21.7 |
| `ucd-snmp` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.2.5-8.AS21.7 |
| `ucd-snmp-devel` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.2.5-8.AS21.7 |
| `ucd-snmp-utils` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.2.5-8.AS21.7 |
| `ucd-snmp` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.2.5-8.AS21.7 |
| `ucd-snmp-devel` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.2.5-8.AS21.7 |
| `ucd-snmp-utils` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.2.5-8.AS21.7 |
| `ucd-snmp` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.2.5-8.AS21.7 |
| `ucd-snmp-devel` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.2.5-8.AS21.7 |
| `ucd-snmp-utils` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.2.5-8.AS21.7 |

Products: Juniper Session and Resource Control, Juniper Src Pe.

## How do I fix CVE-2008-0960?

Upgrade to a fixed version.

## Is CVE-2008-0960 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0960 exists.

Public exploit code:

- SNMPv3 - HMAC Validation error Remote Authentication Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-31381](https://insights.sbomify.com/CVE-2021-31381/): SRC Series: A remote attacker sending a specially crafted query may cause the web server to delete files (medium 6.5)
- [CVE-2021-31352](https://insights.sbomify.com/CVE-2021-31352/): SRC Series: NETCONF over SSH allows negotiation of weak ciphers (medium 5.3)
- [CVE-2021-31380](https://insights.sbomify.com/CVE-2021-31380/): Information disclosure in SRC Series (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0960 and fix it if it is affected.

What it is: CVE-2008-0960 is a critical authentication bypass vulnerability in n/a, published on 10 Jun 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0960 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-0960/ (Markdown: https://insights.sbomify.com/CVE-2008-0960/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-0960
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-0960
- OSV: https://osv.dev/vulnerability/CVE-2008-0960

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-0960/
Summaries are generated and may contain mistakes; the official description above is the record.