Patchfirst
CVE-2008-0960 Public exploit EPSS 68.8%

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)…

No fixed version listed yet.Check the vendor advisory. References ↓

Summary

The SNMPv3 HMAC verification in multiple SNMP implementations, including Net-SNMP, UCD-SNMP, eCos, Juniper SRC, NetApp Data ONTAP, SNMP Research, several Cisco IOS, CatOS, ACE and Nexus products, Ingate Firewall and SIParator, and HP OpenView SNMP Emanate Master Agent, trusts the client to specify the HMAC length. An attacker with network access to an affected SNMP service can bypass SNMP authentication by supplying a length value of 1, because the verification only checks the first byte of the HMAC.

Official description · CVE.org

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.

Breakdown
26.2 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15

Public exploit code (Exploit-DB) appeared 2 days after disclosure. No confirmed exploitation is recorded.

  1. Disclosedday 0
  2. Public exploit codeExploit-DB+2 days

What security researchers reported

Not named in any threat report yet

Also mentioned in 3 community threat pulses (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

References

64 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close