⚠ Known Exploited Vulnerability (KEV) Tracker

Description

A vulnerability in the IP packet processing of Cisco Access Point (AP) Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to insufficient input validation of certain IPv4 packets. An attacker could exploit this vulnerability by sending a crafted IPv4 packet either to or through an affected device. A successful exploit could allow the attacker to cause an affected device to reload unexpectedly, resulting in a DoS condition. To successfully exploit this vulnerability, the attacker does not need to be associated with the affected AP. This vulnerability cannot be exploited by sending IPv6 packets.

Lifecycle Timeline

• 2024-03-27
  CVE published

  Entered the public CVE record.

  CVE.org →
• 2024-03-29
  First national advisory 2 days later

  CERT-EU — 2024-031: High Severity Vulnerabilities in Cisco Products

  CyberzSOC advisory index →
• not recorded
  Public exploit code

  No dated exploit found in Metasploit, Exploit-DB or public GitHub repositories.
• not recorded
  EPSS flags exploitation risk

  Tracked, and has never reached 10% (peak 0.6%).
• not recorded
  Added to CISA KEV

  Not in the CISA KEV catalog.
• not recorded
  Federal remediation due

  No remediation deadline set.
• not recorded
  Vendor fix published

  No dated vendor fix. Only Microsoft publishes a machine-readable release date; other vendors state a fixed version without one.

Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 142 points from 2024-03-30, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 0.6% on 2026-06-20.

Published Applicability

Check whether a specific version is affected →

What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.

Research & News Coverage

No mentions found in monitored research blogs or news feeds.

Detection & Exploitation

Blind spot. No public detection — verify by version/patch. Nothing in the monitored scanner, IDS, SIEM or offensive-tool collections references this CVE, so exposure has to be established from asset inventory and patch level rather than from a signature.

Coverage across public collections only: Nuclei and OpenVAS NVT (scan); Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM); Metasploit, Exploit-DB and public GitHub repositories (exploit). Absence here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by PoC-in-GitHub (CC0) and are not vetted: some are fakes and some are malware. Treat them as evidence that code was published, not as code to run.
OpenVAS coverage derives from the Greenbone Community Feed, made available under the Open Database License (ODbL) v1.0; its individual Vulnerability Tests are licensed GNU GPL v2.

CISA Assessment (Vulnrichment / SSVC)

D3FEND Countermeasures

Defensive techniques inferred by MITRE D3FEND from the underlying weakness (CWE-20) — general hardening and detection guidance for this weakness class, not a vendor patch for this specific CVE.

Listed By

Referenced in Advisories

Weaponization Timeline — Offensive & Testing Tools

No exploit-tool sightings recorded for this CVE.

Evidence tiers are explained on the About page — a merged Metasploit module is far stronger evidence than a distro package mention.

External References

CVE.org record → NVD entry → FortiGuard Labs → Rapid7 AttackerKB →