CVE-2024-24426
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 · uneditedReachable assertions in the NGAP_FIND_PROTOCOLIE_BY_ID function of OpenAirInterface Magma v1.8.0 and OAI EPC Federation v1.2.0 allow attackers to cause a Denial of Service (DoS) via a crafted NGAP packet.
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 · moderate confidenceThis is a reachable assertion vulnerability in the NGAP (NG Application Protocol) handling code of OpenAirInterface's Magma and EPC implementations. The NGAP_FIND_PROTOCOLIE_BY_ID function contains assertions that can be triggered by sending specially crafted NGAP packets, causing the process to crash and resulting in a Denial of Service.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 OpenAirInterface installationLook for OpenAirInterface executables, services, or source code directories. Common locations: /usr/local/bin/oai-*, /opt/oai, or check systemctl for oai services. Look for processes named 'mme', 'sgwc', 'spgwc', 'amf', or similar EPC/5G core components.Affected if OpenAirInterface Magma or EPC software is installed and running
-
Determine installed OpenAirInterface versionCheck the version of the installed OAI software. Run 'oai-mme --version' or 'amf --version' if available, or check RPM/deb packages with 'dpkg -l | grep -i oai' or 'rpm -qa | grep -i oai'. Compare against any available version information from the OpenAirInterface project.Affected if The installed version predates the patch for this vulnerability
-
Verify NGAP protocol handling is enabledNGAP is used in 4G MME and 5G AMF components for control plane communication. Check if the MME or AMF service is running and processing NGAP connections. Look for configuration files enabling N11/N2 interfaces.Affected if NGAP message processing is enabled and the service is exposed to network traffic
-
Confirm NGAP_FIND_PROTOCOLIE_BY_ID function is presentIf you have access to the source code or binaries, search for the function 'NGAP_FIND_PROTOCOLIE_BY_ID' in the codebase or binary. In source: 'grep -r "NGAP_FIND_PROTOCOLIE_BY_ID" .' In binaries: 'strings <binary> | grep NGAP_FIND_PROTOCOLIE_BY_ID'Affected if The vulnerable assertion function exists in the deployed code
A system is affected if it runs OpenAirInterface EPC or Magma with NGAP processing enabled and the installed version contains the NGAP_FIND_PROTOCOLIE_BY_ID assertion vulnerability.
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 dataImplement proper error handling to replace assertions in the NGAP_FIND_PROTOCOLIE_BY_ID function with graceful error returns. Update to patched versions when available from the OpenAirInterface project.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24426 — 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-24426 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