CVE-2022-24805 is a medium severity buffer overflow in net-snmp's handling of the NET-SNMP-VACM-MIB INDEX, scored 6.5. A user with read-only credentials can trigger an out-of-bounds memory access. Versions before 5.9.2 are affected and 5.9.2 contains the fix. Upgrade or install your distribution's patched package.
What's affected
The net-snmp project says versions prior to 5.9.2 are affected and that 5.9.2 contains a patch. The Gentoo advisory GLSA 202210-29, which covers this CVE alongside five siblings (CVE-2022-24806 to CVE-2022-24810), lists affected versions as anything before 5.9.2 and unaffected as 5.9.2 and later.
The NVD record also lists Fedora 36 and Debian 10 and 11 packages. Distributions backport fixes, so a package that still reads as 5.9.1 or similar may be patched. Check your distribution's security tracker or changelog instead of relying on the upstream version number alone.
There is a severity difference to be aware of. NVD scores this flaw 6.5, Medium, with a network vector, low privileges and high integrity impact. Gentoo's advisory labels the group low severity, exploitable remotely, and says the worst case is a denial of service. The two agree that the flaw needs valid SNMP credentials.
The record's kev flag is false.
Weakness class per the record: CWE-120.
How to check if you're exposed
Find the installed version and any patch notes.
snmpd -v
snmpwalk -V
On Debian or Ubuntu style systems, check the package changelog for the CVE id:
dpkg -l | grep -i snmp
apt changelog snmpd | grep -i CVE-2022-24805
On RPM based systems:
rpm -q net-snmp
rpm -q --changelog net-snmp | grep CVE-2022-24805
Also check where net-snmp is bundled inside appliances or containers. The free in-browser dependency scan at gold.safeguard.sh/scan can show whether it appears in a manifest you upload.
What to do now
- Inventory hosts and images running snmpd or linking libnetsnmp.
- Upgrade to net-snmp 5.9.2 or later, or install your distribution's patched package and confirm through the changelog.
- Follow the project's guidance: use strong SNMPv3 credentials and do not share them.
- If you must use SNMPv1 or v2c, use a complex community string and restrict access to a known address range.
Why it matters
The flaw is a classic buffer overflow (CWE-120). The code that handles the index of the VACM access control MIB did not check lengths properly, so a crafted request can read or write outside the intended memory.
Because the attacker needs credentials, many teams will rank it low. That is reasonable where SNMP is limited to monitoring hosts and strong v3 credentials are used. It is less comfortable where SNMP v2c community strings such as a read-only string are reused across many devices.
Management protocols tend to be forgotten after setup, so a quick fix often depends on finding where net-snmp is running at all. An inventory pass finds more than a patch pass.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Do I need credentials to hit this bug?
Yes. The project says a user with read-only credentials can exploit it, so the exposure depends on who holds SNMP credentials or community strings.
Sources
Last reviewed: 19 October 2026.