CVE-2014-2310
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 AgentX subagent in Net-SNMP before 5.4.4 allows remote attackers to cause a denial of service (hang) by sending a multi-object request with an Object ID (OID) containing more subids than previous requests, a different vulnerability than CVE-2012-6151.
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 confidenceThe AgentX subagent in Net-SNMP versions before 5.4.4 contains a vulnerability where processing multi-object requests with OIDs containing more subids than previous requests causes the agent to hang, resulting in denial of service. This is a parsing/handling flaw in the AgentX protocol implementation that can be triggered remotely.
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.4CVSS 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.
-
Identify Net-SNMP installation and versionRun 'snmpd -v' or 'net-snmp-config --version' to determine the installed Net-SNMP version. On Linux systems, also check '/usr/sbin/snmpd -V' or query the package manager (e.g., 'rpm -q net-snmp' or 'dpkg -l net-snmp').Affected if The installed version is less than 5.4.4 (for example, 5.4, 5.3.x, or earlier)
-
Confirm AgentX subagent functionality is in useExamine the Net-SNMP configuration file (typically '/etc/snmp/snmpd.conf') for 'agentxsocket' or 'master agentx' directives, or check running processes for AgentX-related subagent connections.Affected if AgentX subagent support is explicitly configured or a custom subagent is connecting to the master agent via AgentX protocol
-
Verify AgentX socket configuration existsInspect the snmpd.conf for lines containing 'agentx' keywords, or check if the environment variable 'SNMP_AGENTX_SOCKET' is set in the environment running snmpd.Affected if An AgentX socket is configured and the service is restarted with this configuration
-
Check for multi-object request handlingReview any custom AgentX subagent code or third-party subagents for their handling of OID processing, particularly where OIDs with varying numbers of subidentifiers are processed sequentially.Affected if A custom or third-party AgentX subagent processes OIDs where subsequent requests contain more subids than previous requests
The system is affected if Net-SNMP version is below 5.4.4 AND AgentX subagent functionality is enabled and processing multi-object requests with variable-length OIDs.
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.4.4 or later to patch the vulnerability. Ensure any custom AgentX subagents are also updated or rebuilt against the fixed library.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2310 — 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-2310 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