dbcve.org
SnmptrapdApplication · Carnegie Mellon University

CVE-2006-0250

MEDIUM · 6.4 CVSS v2.0 Published 2006-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Format string vulnerability in the snmp_input function in snmptrapd in CMU SNMP utilities (cmu-snmp) allows remote attackers to execute arbitrary code by sending crafted SNMP messages to UDP port 162.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A format string vulnerability exists in the snmp_input function of snmptrapd in CMU SNMP utilities (cmu-snmp). The vulnerability allows remote attackers to execute arbitrary code by sending crafted SNMP messages to UDP port 162, exploiting improper format string handling in user-supplied input.

MitigationUpgrade to a patched version of cmu-snmp that properly sanitizes format strings in the snmptrapd snmp_input function, or implement network filtering to limit SNMP trap reception to trusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SnmptrapdApplication
Affected:= 3.6= 3.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if snmptrapd is installed
    Look for the snmptrapd binary on the system using 'which snmptrapd' or check the package manager for cmu-snmp (e.g., rpm -qa | grep -i cmu or dpkg -l | grep -i cmu)
    Affected if snmptrapd from the cmu-snmp package is found on the system
  2. Determine the installed version of cmu-snmp or snmptrapd
    Run snmptrapd with --version, or check the package version (e.g., rpm -q cmu-snmp or dpkg -s cmu-snmp)
    Affected if The version is 3.6 or 3.7 specifically
  3. Verify if snmptrapd process is running
    Check running processes for snmptrapd (e.g., ps aux | grep snmptrapd or pgrep snmptrapd)
    Affected if snmptrapd process is currently active
  4. Confirm snmptrapd is bound to UDP port 162
    Check listening ports for UDP 162 (e.g., netstat -uan | grep 162, ss -uan | grep 162, or nmap -sU -p 162 localhost)
    Affected if snmptrapd is listening on UDP port 162

The system is affected if cmu-snmp snmptrapd version 3.6 or 3.7 is installed and configured to receive SNMP traps on UDP port 162.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of cmu-snmp that properly sanitizes format strings in the snmptrapd snmp_input function, or implement network filtering to limit SNMP trap reception to trusted sources.

Fix this in Snmptrapd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-0250 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-0250 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data