CVE-2024-24458
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 · uneditedAn invalid memory access when handling the ENB Configuration Transfer messages containing invalid PLMN Identities in Athonet vEPC MME v11.4.0 allows attackers to cause a Denial of Service (DoS) to the cellular network by repeatedly initiating connections and sending a crafted payload.
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 confidenceInvalid memory access vulnerability in Athonet vEPC MME v11.4.0 when processing ENB Configuration Transfer messages containing malformed PLMN Identities. Attackers can trigger memory corruption by sending crafted payloads with invalid PLMN data, causing the MME to crash and resulting in cellular network-wide DoS.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Verify Athonet vEPC MME versionAccess the MME administration interface or command line and retrieve the installed software version using 'show version' or equivalent command. Compare against v11.4.0.Affected if The installed version is v11.4.0 of Athonet vEPC MME.
-
Confirm S1-MME interface is enabledCheck MME configuration for S1-MME interface status. This is typically found in the MME network settings or interface configuration section. Verify the interface is in 'enabled' or 'active' state.Affected if The S1-MME interface is enabled and the MME is reachable from the eNB network.
-
Verify ENB Configuration Transfer handling is activeCheck MME configuration for ENB Configuration Transfer message processing. Look for settings related to ENB configuration transfer, neighbor relation management, or S1 setup configuration.Affected if ENB Configuration Transfer message handling is enabled in the MME configuration.
-
Inspect PLMN Identity validation settingsExamine MME configuration for PLMN Identity validation or filtering settings. Look for fields controlling PLMN format checking in the ENB or neighbor relation configuration.Affected if PLMN Identity validation is disabled, not configured, or set to permissive mode.
-
Check for crash logs or service interruptionsReview MME system logs, crash dumps, or alarm history for recent memory corruption events, process restarts, or unexpected MME service interruptions.Affected if Recent crashes or restarts of the MME service are present in logs.
A user is affected if running Athonet vEPC MME v11.4.0 with S1-MME and ENB Configuration Transfer enabled, and PLMN validation is not enforced.
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 patch from Athonet for vEPC MME; implement input validation for PLMN Identity fields in ENB Configuration Transfer message handling to reject malformed data before memory allocation. Consider network segmentation and traffic filtering as interim controls.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24458 — 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-24458 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