CVE-2022-24810 is a medium severity NULL pointer dereference in net-snmp, scored 6.5. A user with read-write credentials can send a malformed OID in a SET to the nsVacmAccessTable. Versions before 5.9.2 are affected. Upgrade to 5.9.2 or install your distribution's patched package.
What's affected
The project says versions prior to 5.9.2 are affected and that 5.9.2 contains the patch. Gentoo's advisory GLSA 202210-29 gives the same boundary, with versions at or above 5.9.2 unaffected, and groups this CVE with five related net-snmp issues.
The NVD record lists Debian 10 and Fedora 36 among the affected distributions. Distribution maintainers backport fixes without changing the upstream version, so confirm with your distribution's tracker or package changelog.
NVD scores the flaw 6.5 with a network vector and low privileges. Gentoo calls the group low severity and says the worst result could be denial of service. A null pointer dereference normally crashes the process, which matches that description. The CVSS vector in NVD, though, records high integrity impact and no availability impact, which sits oddly with a crash. If you track both numbers, note that they do not line up.
No exploitation in the wild is recorded; kev is false.
Weakness class per the record: CWE-476.
How to check if you're exposed
Check the net-snmp version and search your package changelog for the CVE id:
snmpd -v
rpm -q --changelog net-snmp | grep CVE-2022-24810
apt changelog snmpd | grep CVE-2022-24810
Then check how SNMP write access is configured. The flaw needs read-write credentials, so look for write communities or SNMPv3 users with write views in snmpd.conf:
grep -nE 'rwcommunity|rwuser|rwcommunity6' /etc/snmp/snmpd.conf
If you find none, the attack path described by the project is not open. Still plan to patch.
What to do now
- List hosts running snmpd and note their version.
- Upgrade to net-snmp 5.9.2 or later, or apply your distribution's patched build.
- Remove read-write SNMP access that nobody uses and keep strong SNMPv3 credentials for the rest.
- Restrict SNMP access to specific management addresses.
Why it matters
A NULL pointer dereference (CWE-476) occurs when code uses a pointer it assumes is valid. A malformed object identifier in a SET to the VACM access table led to that situation. The usual result is a crash of the SNMP agent.
For monitoring that is a nuisance, but an agent crash can hide a device from your monitoring. If a team relies on SNMP traps and polling to notice failures, losing the agent makes outages harder to see.
The upstream guidance is a good baseline for any SNMP deployment: strong v3 credentials, no shared credentials, and address restrictions for the older versions.
Quick check
Does a read-only credential let someone trigger this?
The project describes this one as needing read-write credentials. The sibling flaw CVE-2022-24805 needs only read-only credentials.
Sources
Last reviewed: 19 October 2026.