CVE-2024-23814
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe integrated ICMP service of the network stack of affected devices can be forced to exhaust its available memory resources when receiving specially crafted messages targeting IP fragment re-assembly. This could allow an unauthenticated remote attacker to cause a temporary denial of service condition of the ICMP service, other communication services are not affected. Affected devices will resume normal operation after the attack terminates.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ICMP service in affected network devices has a memory exhaustion vulnerability in its IP fragment re-assembly handling. An unauthenticated remote attacker can send specially crafted ICMP messages that cause the service to consume all available memory, resulting in temporary denial of service. The device automatically recovers after the attack stops.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device and firmware versionAccess the device management interface (CLI, web UI, or SNMP) and retrieve the firmware/software version. For CLI, common commands include 'show version', 'system info', or 'ver'. Compare this version against the vendor's published list of affected versions for CVE-2024-23814.Affected if The installed firmware version falls within the vendor-disclosed vulnerable version range.
-
Verify ICMP service is enabledCheck the device configuration for ICMP service status. In CLI, commands like 'show ip icmp', 'show running-config | include icmp', or 'show service' may reveal if ICMP is enabled. ICMP must be active for this vulnerability to be exploitable.Affected if ICMP service is enabled and processing incoming packets.
-
Confirm IP fragment reassembly is activeInspect device configuration for IP fragment reassembly settings. Look for parameters related to fragment handling, reassembly buffers, or 'fragment-reassembly' in the config. This feature processes fragmented packets including ICMP.Affected if IP fragment reassembly is enabled (default behavior on most devices).
-
Check for existing ICMP rate limiting or filteringReview firewall, ACL, or traffic shaping configurations for ICMP-specific rate limits or filters. Commands such as 'show access-lists', 'show rate-limit', or examining the firewall policy can reveal if mitigations are already in place.Affected if No ICMP rate limiting or filtering is configured, leaving the ICMP service exposed to crafted packets.
A device is affected if it runs a firmware version within the vendor-specified vulnerable range AND has ICMP service enabled with IP fragment reassembly active and no ICMP-specific rate limiting configured.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware updates when available; implement network-level ICMP rate limiting or filtering to mitigate exploitation until patches are applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23814 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data