MME crash via unchecked missing TAI field
Published Jan 21, 2025 · Updated Mar 24, 2025
A null pointer dereference in Magma MME 1.8.0 and earlier allows network-adjacent attackers to crash the service via malformed S1AP input. In s1ap_mme_handle_initial_ue_message, a failed lookup leaves ie null when TAI is absent, but OCTET_STRING_TO_TAC dereferences it. Access to the S1 interface is required; no credentials or user interaction are needed, and repeated malformed messages can prolong the MME outage.
Summary
What happened
A null pointer dereference in Magma MME 1.8.0 and earlier allows network-adjacent attackers to crash the service via malformed S1AP input. In s1ap_mme_handle_initial_ue_message, a failed lookup leaves ie null when TAI is absent, but OCTET_STRING_TO_TAC dereferences it. Access to the S1 interface is required; no credentials or user interaction are needed, and repeated malformed messages can prolong the MME outage.
The record
- CVE
- CVE-2023-37034
- Published
- Jan 21, 2025
- Updated
- Mar 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2025CVE publishedPublication date reported by the CVE source.
- Mar 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo