Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

NULL pointer dereference in net-snmp GET-NEXT handling of nsVacmAccessTable

IdentifiersCVE-2022-24809CWE-476· NULL Pointer Dereference

CVE-2022-24809 affects net-snmp prior to version 5.9.2. A user with read-only SNMP credentials can send a malformed OID in a GET-NEXT request targeting the nsVacmAccessTable, which triggers a NULL pointer dereference in the agent and causes the SNMP service to crash or become unresponsive. The issue is described as affecting net-snmp tooling related to SNMP and was noted by Citrix as impacting XenServer 8 through its use of net-snmp.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in denial of service of the SNMP service. The vulnerable process can crash or hang due to the NULL pointer dereference, rendering SNMP management functionality unavailable. In XenServer 8 deployments referenced in the supporting content, an attacker on the management network with read-only credentials may crash or render the host SNMP service unresponsive.

Mitigation

If you can’t patch tonight, do this now.

Use strong SNMPv3 credentials and avoid sharing those credentials. Where SNMPv1 or SNMPv2c must be used, use a complex community string and restrict SNMP access to trusted IP address ranges. More generally, limit exposure of the management network and management interfaces to authorized hosts only until patches are applied.

Remediation

Patch, then assume compromise.

Upgrade net-snmp to version 5.9.2 or later, which contains the vendor patch for this issue. In affected downstream products such as XenServer 8, apply the vendor-provided updates or hotfixes referenced by the platform vendor.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
DebianDebian Linuxoperating_system
Fedora ProjectFedoraoperating_system
Net-SnmpNet-Snmpapplication
Red HatEnterprise Linuxoperating_system
Red HatEnterprise Linux Eusoperating_system
Red HatEnterprise Linux For Arm 64operating_system
Red HatEnterprise Linux For Arm 64 Eusoperating_system
Red HatEnterprise Linux For Ibm Z Systemsoperating_system
Red HatEnterprise Linux For Ibm Z Systems Eusoperating_system
Red HatEnterprise Linux For Power Little Endianoperating_system
Red HatEnterprise Linux For Power Little Endian Eusoperating_system
Red HatEnterprise Linux Server Ausoperating_system
Red HatEnterprise Linux Server For Power Little Endian Update Services For Sap Solutionsoperating_system
Red HatEnterprise Linux Server Update Services For Sap Solutionsoperating_system
Red HatEnterprise Linux Update Services For Sap Solutionsoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.