CVE-2024-24454
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 Modify Request messages 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 parsing the ProtocolIE_ID field of E-RAB Modify Request messages. Attackers can trigger a denial of service by repeatedly initiating connections and sending crafted malformed packets, causing the MME to crash and disrupt cellular network services.
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 installation and versionCheck system inventory, software bills of materials, or run 'dpkg -l'/'rpm -qa' looking for 'athonet' or 'vepc' packages. Also check /opt/athonet or similar vendor installation directories for version files.Affected if The installed version is v11.4.0 and has not been patched.
-
Verify S1-MME interface is enabledCheck MME configuration files (typically in /opt/athonet/mme/config or /etc/athonet) for 's1-mme' or 'S1-MME' interface settings. Look for enabled:true or similar flags.Affected if The S1-MME interface is enabled, as this is the pathway for malformed E-RAB Modify Request packets to reach the MME.
-
Inspect MME logs for crash eventsExamine logs in /var/log/athonet or the MME log directory for sudden process exits, segmentation faults, or memory access errors occurring around the time of incoming E-RAB Modify Request processing.Affected if Logs show unexplained MME crashes or invalid memory access errors without corresponding legitimate network events.
-
Check for vendor patch appliedReview patch management records or the MME version again; some vendors append patch level to version strings (e.g., v11.4.0.1). Compare against the base v11.4.0 release.Affected if The installed version remains at v11.4.0 with no subsequent patch applied.
If the system runs Athonet vEPC MME version 11.4.0 with the S1-MME interface enabled and no vendor patch applied, it is vulnerable to this denial-of-service condition.
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-provided patch for vEPC MME v11.4.0 when released. In the interim, consider implementing S1-MME interface traffic filtering or rate limiting to reduce attack surface, though this may impact legitimate handovers.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24454 — 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-24454 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