Security Advisory

CVE-2002-0013: SNMPv1 Request Flaws (PROTOS)

Last updated:
  • CVE-2002-0013

CVE-2002-0013 covers flaws in how many SNMPv1 agents parse GetRequest, GetNextRequest and SetRequest messages, found by the PROTOS test suite in 2002. A malformed request can crash the agent or give an attacker control, sometimes without the right community string. NVD scores it 10.0 (CVSS v2), and CERT/CC names Cisco, APC, Hirschmann and Juniper devices.

Vulnerability summary

CVSS base score

10

Critical severity

EPSS score (FIRST)

50.8%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2002-0013 · Source: NVD

Affected components

ComponentCPEVersion range
SNMPv1 agents (request handling), many implementationscpe:2.3:a:snmp:snmp:*:*:*:*:*:*:*:*per implementation; NVD lists one generic SNMP CPE (NVD, CERT/CC VU#854306)
Cisco routers and Catalyst switches running Cisco IOS—affected IOS releases per cisco-sa-20020212-snmp-msgs
Cisco CatOS Catalyst switches, PIX firewall, Aironet AP340/AP350, VPN 3000, ONS 15454—per product (cisco-sa-20020211-snmp-msgs-non-ios)
American Power Conversion SNMP-enabled products—some firmware versions; upgrades available (APC statement, CERT/CC VU#854306)
Hirschmann networking products—some products; firmware via Hirschmann support (CERT/CC VU#854306)
Juniper JUNOS—builds before 2002-01-05, only with SNMP PDU tracing enabled (CERT/CC VU#854306)
ucd-snmp (now Net-SNMP)—before 4.2.2 (Net-SNMP statement, CERT/CC VU#854306)

What does this mean for affected devices?

CVE-2002-0013 is the request-handling half of the 2002 PROTOS SNMP disclosure. NVD's record says flaws in "the SNMPv1 request handling of a large number of SNMP implementations allow remote attackers to cause a denial of service or gain privileges via (1) GetRequest, (2) GetNextRequest, and (3) SetRequest messages, as demonstrated by the PROTOS c06-SNMPv1 test suite." NVD scores it 10.0 under CVSS v2, vector AV:N/AC:L/Au:N/C:C/I:C/A:C, a Primary score from NVD itself, and records CWE-264. The record has no CVSS v3 score. It is a multi-vendor entry: its only configuration is a generic SNMP CPE, and NVD notes that the candidate was likely to be split per vendor (NVD).

What did the PROTOS test suite find?

The University of Oulu's Secure Programming Group built the PROTOS c06-SNMPv1 suite of malformed SNMP messages and ran it against many agents. CERT/CC Vulnerability Note VU#854306, published 2002-02-12, reports problems "in both ASN.1 decoding and processing of SNMP request messages", including "denial-of-service conditions, format string vulnerabilities, and buffer overflows." It adds that "some vulnerabilities do not require the request message to use the correct SNMP community string", so a default or secret community does not protect a vulnerable agent. CERT/CC lists where SNMP runs: routers, switches and wireless access points, cable and DSL modems, printers and copiers, medical imaging units and "Manufacturing and Processing Equipment".

Which devices and firmware were named?

The vendor statements in VU#854306 carry the device angle. CERT/CC records 93 vendors as vulnerable, among them:

  • Cisco. cisco-sa-20020212-snmp-msgs covers products running IOS, including the 800 to 4700 series routers, uBR900 cable access routers, Catalyst 2900XL, 2950, 3500XL and 3550 switches and the 7200, 7500 and 12000 series routers. Cisco says malformed SNMP messages cause "a system crash and reload (or reboot) in most circumstances." The companion non-IOS advisory adds CatOS Catalyst switches, the PIX firewall, Aironet AP340 and AP350 access points, the VPN 3000 concentrator and the ONS 15454 optical platform.
  • American Power Conversion. APC said exploiting the flaws "in some versions of our firmware can interfere with the normal operation of APC's SNMP-enabled products" and that upgrades are available.
  • Hirschmann. Hirschmann said some of its networking products are affected and pointed customers to its support centre for firmware releases.
  • Juniper. JUNOS releases built after 2002-01-05 carry the fix; the behaviour reproduced only with snmp traceoptions flag pdu enabled.
  • SNMP stack suppliers. The Net-SNMP project said all ucd-snmp versions before 4.2.2 are susceptible. SNMP Research fixed its products in 15.3.1.7. Wind River found a memory leak in its WindNet SNMP v2.0 binary agent, but none in Envoy 9.x.

That last group matters for firmware today. A vendor that compiled one of those stacks into a device inherited the bug, and only that vendor's firmware release removes it. The companion trap-handling CVE is CVE-2002-0012.

Is CVE-2002-0013 exploited?

CVE-2002-0013 is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.5085, the 98.9th percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS). Cisco wrote that it was not aware of malicious exploitation.

How do you fix or contain it?

Install the device vendor's fixed firmware; for an embedded stack, move to a release the stack supplier says passes PROTOS. Where that is impossible, Cisco's workarounds still describe the containment: turn SNMP off with no snmp-server, or apply an access list that denies UDP ports 161 and 162. Cisco warns that source-address filters can be bypassed by spoofing without ingress filtering. Our SNMP agent vulnerabilities guide explains how to find which SNMP agent a firmware image ships, and why an agent never retested since PROTOS still ranks high. The memory corruption fix guide covers the parser bug class, and CVE-2017-6736 shows a later Cisco IOS SNMP parser flaw that CISA lists as exploited.

How to fix this class of issueNo dedicated SoftWSP guide covers this weakness class; the fix is usually the vendor patch or firmware update referenced above. Our related guide explains how to plan and verify it: NIST SP 800-40 Rev. 4: enterprise patch management planning, explained.

Evidence

  • SNMPv1 request handling of many implementations; DoS or privileges via GetRequest, GetNextRequest, SetRequest; PROTOS c06-SNMPv1; CVSS v2 10.0 Primary ([email protected]); CWE-264; generic SNMP CPE; likely to be split per vendor. — NVD
  • Published 2002-02-12; ASN.1 decoding and request processing; DoS, format string, buffer overflows; some need no correct community; device categories; 93 vendors marked vulnerable; vendor statements from Cisco, APC, Hirschmann, Juniper, NET-SNMP (ucd-snmp before 4.2.2), SNMP Research (15.3.1.7), Wind River (WindNet SNMP v2.0 leak). — CERT/CC VU#854306
  • IOS products listed as vulnerable; malformed messages cause crash and reload; workarounds no snmp-server and ACL on UDP 161/162; spoofing caveat; Cisco not aware of malicious exploitation; final revision 2.2 of 2003-12-23. — Cisco cisco-sa-20020212-snmp-msgs
  • Non-IOS products listed as vulnerable: CatOS Catalyst, PIX, Aironet AP340/AP350, VPN 3000, ONS 15454 and others; revision 2.6 of 2004-03-01. — Cisco cisco-sa-20020211-snmp-msgs-non-ios
  • Not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). — CISA KEV
  • EPSS 0.50845 (98.9th percentile), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CERT/CC VU#854306: Multiple vulnerabilities in SNMPv1 request handling
  3. Cisco Security Advisory: Malformed SNMP Message-Handling Vulnerabilities (IOS)
  4. Cisco Security Advisory: Malformed SNMP Message-Handling Vulnerabilities for Non-IOS Based Products
  5. CISA KEV
  6. FIRST EPSS

Frequently asked questions

Does CVE-2002-0013 need a valid SNMP community string?

Not always. CERT/CC says some of the request-handling flaws do not require the message to carry the correct community string, so a changed or secret community does not protect a vulnerable agent (per CERT/CC VU#854306).

Which devices were affected by CVE-2002-0013?

Cisco IOS routers and Catalyst switches, CatOS switches, PIX firewalls and Aironet access points, APC SNMP-enabled products, Hirschmann networking products and Juniper routers with PDU tracing on, among 93 vendors CERT/CC marked vulnerable (per Cisco and CERT/CC VU#854306).

Why does NVD show only a CVSS v2 score for CVE-2002-0013?

The record dates from 2002 and NVD scored it 10.0 under CVSS v2 as a Primary score; it has no CVSS v3 metric. The guide treats it as high on any agent never retested since PROTOS (per NVD).

Is CVE-2002-0013 in the CISA KEV catalog?

No, not as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.5085, the 98.9th percentile, in the 2026-11-16 dataset (per CISA KEV and FIRST EPSS).