CVE-2024-24453
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 ProtocolIE_ID field of E-RAB NotToBeModifiedBearerModInd information element 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 confidenceAthonet vEPC MME v11.4.0 contains an invalid memory access vulnerability when parsing the ProtocolIE_ID field within the E-RAB NotToBeModifiedBearerModInd information element. Attackers can trigger this by establishing repeated connections and sending specially crafted S1AP messages containing malformed IE data, causing the MME to crash and resulting in cellular network 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.
-
Confirm Athonet vEPC MME is presentIdentify if Athonet vEPC MME software is installed in your environment by checking running processes, installed packages, or system inventory for 'Athonet' or 'vEPC' componentsAffected if Athonet vEPC MME software is installed and running
-
Check MME software versionDetermine the installed version of the Athonet vEPC MME by querying the system, checking software inventory, or using vendor-provided version inspection commandsAffected if The installed version matches 11.4.0 exactly or falls within the affected version range around v11.4.0
-
Verify S1-MME interface is activeCheck if the S1-MME interface is configured and active on the MME, as this is the pathway for S1AP message exchange with eNodeBsAffected if S1-MME interface is enabled and accepting S1AP connections from eNodeBs
-
Look for MME crash indicatorsReview system logs, MME process logs, and any core dump files for signs of recent MME crashes or memory access faults, particularly those mentioning S1AP or E-RAB processingAffected if Recent MME crashes or memory errors are logged, especially related to S1AP message handling
If Athonet vEPC MME version 11.4.0 is running with an active S1-MME interface, the environment is likely affected by this 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 dataContact Athonet for vendor-specific patch v11.4.0 or later; implement network-level S1AP message validation and rate limiting on S1-MME interfaces as a compensating control until patch is available.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24453 — 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-24453 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