Security Advisory

CVE-2002-0012: SNMPv1 Trap Handling Flaws (PROTOS)

Last updated:
  • CVE-2002-0012

CVE-2002-0012 covers flaws in how many SNMP implementations parse SNMPv1 trap messages, found by the PROTOS test suite in 2002. A malformed trap can crash the receiving software or give an attacker control of the device. NVD scores it 10.0 (CVSS v2), and CERT/CC and Cisco name affected Cisco, APC, Hirschmann and Juniper products.

Vulnerability summary

CVSS base score

10

Critical severity

EPSS score (FIRST)

23.9%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

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

Affected components

ComponentCPEVersion range
SNMPv1 trap handling, many implementationscpe:2.3:a:snmp:snmp:*:*:*:*:*:*:*:*per implementation; NVD lists one generic SNMP CPE (NVD, CERT/CC VU#107186)
Cisco routers and Catalyst switches running Cisco IOS—affected IOS releases per cisco-sa-20020212-snmp-msgs
Cisco CatOS Catalyst switches, PIX firewall, Aironet access points, 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#107186)
Hirschmann networking products—some products; firmware via Hirschmann support (CERT/CC VU#107186)
Juniper JUNOS—builds before 2002-01-05, only with SNMP PDU tracing enabled (CERT/CC VU#107186)
ucd-snmp (now Net-SNMP)—before 4.2.2 (Net-SNMP statement, CERT/CC VU#107186)

What does this mean for affected devices?

CVE-2002-0012 is the trap-handling half of the 2002 PROTOS SNMP disclosure. NVD's record says flaws in "a large number of SNMP implementations allow remote attackers to cause a denial of service or gain privileges via SNMPv1 trap handling, 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, and its only configuration is a generic SNMP CPE; NVD notes that the candidate was likely to be split per vendor (NVD).

Where does SNMP trap handling run?

Traps are the notifications an agent sends to a manager on UDP port 162. The code that parses them sits in network management stations and trap receivers, and also in devices that receive or forward traps. CERT/CC Vulnerability Note VU#107186, first published on 2002-01-16 and made public on 2002-02-12, says multiple vendors' "SNMPv1 Trap handling implementations contain vulnerabilities that may allow unauthorized privileged access, denial-of-service conditions, or unstable behavior", and that the impact "may allow an attacker to gain access to the affected device." The parsing faults are the same kind PROTOS found in request handling (CVE-2002-0013): ASN.1 decoding errors, format string bugs and buffer overflows.

Which devices and firmware were named?

CERT/CC records 91 vendors as vulnerable in VU#107186. The vendor statements give the device angle:

  • Cisco. Both Cisco advisories list CVE-2002-0012 alongside CVE-2002-0013. cisco-sa-20020212-snmp-msgs covers routers and Catalyst switches running IOS, where malformed SNMP messages cause "a system crash and reload (or reboot) in most circumstances." The non-IOS advisory adds CatOS Catalyst switches, the PIX firewall, Aironet access points, the VPN 3000 concentrator and the ONS 15454 optical platform.
  • American Power Conversion. APC said the flaws "in some versions of our firmware can interfere with the normal operation of APC's SNMP-enabled products," with upgrades available.
  • Hirschmann. Some of its networking products are affected; firmware comes through Hirschmann support.
  • Juniper. Fixed in JUNOS builds after 2002-01-05, and reproducible only with SNMP PDU tracing enabled.
  • SNMP stack suppliers. Net-SNMP said ucd-snmp before 4.2.2 is susceptible, SNMP Research fixed its products in 15.3.1.7, and Wind River reported a memory leak in the WindNet SNMP v2.0 binary agent.

A device that embeds one of those stacks, or a trap receiver such as snmptrapd, inherits the flaw until its vendor ships a fixed build. Trap receivers remain a live surface: Net-SNMP's 2025 snmptrapd overflow, CVE-2025-68615, is the same class in the same component.

Is CVE-2002-0012 exploited?

CVE-2002-0012 is not in the CISA KEV catalog as of 2026-11-17 (catalog version 2026.11.13). FIRST EPSS gives it 0.2391, the 97.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 vendor's fixed firmware or move the embedded SNMP stack to a release its supplier says passes PROTOS. Where a device does not need to receive traps, do not run a trap receiver at all, and block UDP 162 at the interface. Cisco's workarounds are to turn SNMP off or to deny UDP 161 and 162 with an access list. Our SNMP agent vulnerabilities guide shows how to find snmptrapd and the SNMP stack in a firmware image and how to rank these CVEs. The memory corruption fix guide covers the parser bug class, and CVE-2025-20352 is a current Cisco IOS SNMP 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 trap handling of many implementations; DoS or privileges; PROTOS c06-SNMPv1; CVSS v2 10.0 Primary ([email protected]); CWE-264; generic SNMP CPE; likely to be split per vendor. — NVD
  • First published 2002-01-16, date public 2002-02-12; trap handling flaws allow privileged access, DoS or unstable behaviour; may give access to the device; 91 vendors marked vulnerable; statements from Cisco, APC, Hirschmann, Juniper, NET-SNMP, SNMP Research, Wind River. — CERT/CC VU#107186
  • IOS advisory names CAN-2002-0012 and CAN-2002-0013; crash and reload; workarounds; Cisco not aware of malicious exploitation. — Cisco cisco-sa-20020212-snmp-msgs
  • Non-IOS advisory names CVE-2002-0012 and CVE-2002-0013; CatOS Catalyst, PIX, Aironet, VPN 3000, ONS 15454 listed vulnerable. — 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.23907 (97.9th percentile), dataset 2026-11-16, read 2026-11-17. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CERT/CC VU#107186: Multiple vulnerabilities in SNMPv1 trap 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

What is the difference between CVE-2002-0012 and CVE-2002-0013?

Both come from the PROTOS c06-SNMPv1 test suite. CVE-2002-0012 covers SNMPv1 trap handling (CERT/CC VU#107186); CVE-2002-0013 covers GetRequest, GetNextRequest and SetRequest handling (VU#854306) (per NVD).

Which devices were affected by CVE-2002-0012?

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

How do I reduce exposure if the firmware cannot be updated?

Do not run a trap receiver where it is not needed, and block UDP 162, and UDP 161 if SNMP is unused, at the interface. Cisco also documents turning SNMP off entirely (per Cisco cisco-sa-20020212-snmp-msgs).

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

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