dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-24806

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-16
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

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
net-snmp provides various tools relating to the Simple Network Management Protocol. Prior to version 5.9.2, a user with read-write credentials can exploit an Improper Input Validation vulnerability when SETing malformed OIDs in master agent and subagent simultaneously. Version 5.9.2 contains a patch. Users should use strong SNMPv3 credentials and avoid sharing the credentials. Those who must use SNMPv1 or SNMPv2c should use a complex community string and enhance the protection by restricting access to a given IP address range.

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
How this class of weakness works · CWE-20

The application accepts input without confirming it is well-formed or within expected bounds, so malformed data can push the program into states its author never anticipated. Attackers probe these gaps to trigger crashes, bypass logic, or feed tainted values into more dangerous operations downstream. Remediating it well means validating and normalising every input at the boundary against a strict allow-list — not merely filtering known-bad values.

General guidance for the improper input validation class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
FedoraOperating system
Affected:= 35= 36
Debian LinuxOperating system
Affected:= 10.0= 11.0
Enterprise LinuxOperating system
Affected:= 9.0
Enterprise Linux EusOperating system
Affected:= 9.2= 9.4
Enterprise Linux For Arm 64Operating system
Affected:= 9.0= 9.2_aarch64= 9.4_aarch64
Enterprise Linux For Arm 64 EusOperating system
Affected:= 9.4_aarch64
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 9.0= 9.2_s390x= 9.4_s390x
Enterprise Linux For Ibm Z Systems EusOperating system
Affected:= 9.4_s390x

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Recommended fix High confidence

net-snmp version 5.9.2

  1. Check the current net-snmp version installed: rpm -qa | grep net-snmp or dpkg -l | grep snmp
  2. Update the package repository metadata: dnf check-update (RHEL/Fedora) or apt-get update (Debian)
  3. Upgrade net-snmp to version 5.9.2 or later: dnf update net-snmp (RHEL/Fedora) or apt-get install snmp (Debian)
  4. Verify the installed version after upgrade: snmpd -V
  5. If the fixed version is not available in default repositories, consider enabling EPEL (RHEL) or backports repository (Debian), or compile from source using the fixed commit ce66eb97c17aa9a48bc079be7b65895266fa6775
  6. Restart the snmpd service after upgrade: systemctl restart snmpd
  7. As a secondary mitigation, configure SNMPv3 with strong credentials instead of SNMPv1/v2c community strings, or restrict access by IP address in snmpd.conf
Caveat Upgrading net-snmp may require configuration adjustments; ensure snmpd.conf is compatible with the new version before restarting services

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,600. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24806 — 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-2022-24806 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