CVE-2014-2284
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 · uneditedThe Linux implementation of the ICMP-MIB in Net-SNMP 5.5 before 5.5.2.1, 5.6.x before 5.6.2.1, and 5.7.x before 5.7.2.1 does not properly validate input, which allows remote attackers to cause a denial of service via unspecified vectors.
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 · moderate confidenceThe Linux ICMP-MIB implementation in Net-SNMP versions 5.5.x before 5.5.2.1, 5.6.x before 5.6.2.1, and 5.7.x before 5.7.2.1 contains improper input validation, allowing remote unauthenticated attackers to cause denial of service via malformed SNMP packets to the ICMP-MIB subsystem.
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= 5.5= 5.5.0.1= 5.5.0.2= 5.5.1= 5.5.1.1= 5.5.2= 5.6= 5.6.1.1= 5.6.2= 5.7= 5.7.1= 5.7.2CVSS 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
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check if snmpd process is runningRun 'ps aux | grep snmpd' or 'systemctl status snmpd' to see if the Net-SNMP daemon is activeAffected if snmpd is running and exposed to network
-
Identify installed Net-SNMP versionRun 'snmpd -V' or 'snmp_version=$(snmpget -V 2>&1 | head -1)' to retrieve the version numberAffected if version is 5.5.x before 5.5.2.1, 5.6.x before 5.6.2.1, or 5.7.x before 5.7.2.1 (specifically 5.5, 5.5.0.1, 5.5.0.2, 5.5.1, 5.5.1.1, 5.5.2, 5.6, 5.6.1.1, 5.6.2, 5.7, 5.7.1, or 5.7.2)
-
Verify SNMP service is listening on networkRun 'netstat -ulnp | grep 161' or 'ss -ulnp | grep 161' to check if UDP port 161 is bound to a network interfaceAffected if SNMP is listening on a reachable network interface rather than localhost only
-
Test ICMP-MIB accessibilityRun 'snmpwalk -v2c -c public localhost ICMP-MIB::icmp' or query OID 1.3.6.1.2.1.5 to see if ICMP-MIB is accessibleAffected if ICMP-MIB responds to SNMP queries (vulnerability requires ICMP-MIB to be accessible)
You are affected if Net-SNMP version 5.5.x before 5.5.2.1, 5.6.x before 5.6.2.1, or 5.7.x before 5.7.2.1 is running and the ICMP-MIB is accessible via SNMP over the network.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Net-SNMP to version 5.5.2.1, 5.6.2.1, or 5.7.2.1 or later. If immediate patching is not feasible, restrict network access to UDP port 161 (SNMP) using firewalls or ACLs to limit exposure to untrusted networks.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2284 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2284 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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