# CVE-2022-24809: net-snmp: A malformed OID in a SET request to NET-SNMP-AGENT-MIB::nsLogTable can cause a NULL pointer dereference

> A remote attacker with read-only credentials can cause a denial of service in net-snmp by sending a malformed OID in a GET-NEXT request.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2024
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2022-24809, DEBIAN-CVE-2022-24809, UBUNTU-CVE-2022-24809

## What is CVE-2022-24809?

CVE-2022-24809 is a medium-severity vulnerability in Debian Debian Linux, published on 16 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

net-snmp provides various tools relating to the Simple Network Management Protocol. Prior to version 5.9.2, a user with read-only credentials can use a malformed OID in a `GET-NEXT` to the `nsVacmAccessTable` to cause a NULL pointer dereference. 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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2022-24809?

It affects 15 products.


Products: Debian Debian Linux, Fedoraproject Fedora, Net-Snmp Net-Snmp, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux for Arm 64, Redhat Enterprise Linux for Arm 64 Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Little Endian, Redhat Enterprise Linux for Power Little Endian Eus, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server for Power Little Endian Update Services for Sap Solutions, Redhat Enterprise Linux Server Update Services for Sap Solutions, Redhat Enterprise Linux Update Services for Sap Solutions.

## How do I fix CVE-2022-24809?

Upgrade to a fixed version.

## Is CVE-2022-24809 being exploited?

There is no known exploitation of CVE-2022-24809 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24809 and fix it if it is affected.

What it is: CVE-2022-24809 is a medium-severity vulnerability in Debian Debian Linux, published on 16 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24809 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24809/ (Markdown: https://insights.sbomify.com/CVE-2022-24809/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24809
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24809
- OSV: https://osv.dev/vulnerability/CVE-2022-24809

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24809/
Summaries are generated and may contain mistakes; the official description above is the record.