CVE-2024-24424
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 · uneditedA reachable assertion in the decode_access_point_name_ie function of Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) allows attackers to cause a Denial of Service (DoS) via a crafted NAS 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 · high confidenceA reachable assertion in the decode_access_point_name_ie function of Magma's NAS (Non-Access Stratum) protocol parser allows remote attackers to trigger a denial of service by sending a crafted Access Point Name (APN) Information Element within a malicious NAS packet. The vulnerability exists in Magma versions 1.8.0 and earlier, stemming from insufficient validation of the APN IE data structure before an assertion check.
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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 Magma installationRun 'magmad --version' or check package manager for installed magma version (e.g., dpkg -l | grep magma, rpm -qa | grep magma)Affected if Magma is installed and version is 1.8.0 or earlier
-
Verify NAS protocol parser is activeCheck running processes for magmad or nas-related services: ps aux | grep -E 'magmad|nas' and check if the service is listening on S1AP or NAS-related ports (typically port 36412 for S1AP)Affected if NAS parser service is running and accepting connections
-
Confirm external NAS packet ingressReview networkACLs/firewall rules to determine if NAS packets from untrusted sources can reach the Magma MME or mobility management componentAffected if External NAS packets from non-operator sources are permitted to reach the Magma service
You are affected if Magma version 1.8.0 or earlier is installed and the NAS protocol parser service is actively accepting external NAS packets on the network.
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.
dbcve · scopedUpgrade Magma to version 1.9 or later (commit 08472ba98b8321f802e95f5622fa90fec2dea486) to apply the patch that adds proper bounds checking before the assertion in decode_access_point_name_ie. If immediate upgrade is not feasible, implement network-level filtering to reject malformed NAS packets at the ingress point.
Magma v1.9
- 1. Identify all deployments running Magma version 1.8.0 or earlier.
- 2. Plan an upgrade to Magma v1.9 or later, which contains the fix for the reachable assertion in decode_access_point_name_ie (commit 08472ba98b8321f802e95f5622fa90fec2dea486).
- 3. Before upgrading, review the Magma v1.9 release notes and changelog for any known issues or migration requirements.
- 4. Perform the upgrade following the standard Magma upgrade procedure for your deployment type.
- 5. After upgrading, verify that the NAS packet parsing no longer triggers the assertion and that services are functioning normally.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24424 — 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-24424 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