Baseband memory corruption via oversized emergency number
Published Mar 13, 2023 · Updated Mar 3, 2025
Heap-based buffer overflow in Samsung Exynos 5G MM message codecs allows remote authenticated users to corrupt baseband memory. NrmmMsgCodec allocates 22 bytes per emergency number but accepts a declared length up to 255 bytes and expands each encoded byte into two output bytes without enforcing that limit. Triggering the flaw requires a malicious mobile network operator or local access; the overwrite causes a baseband crash and limited memory alteration or exposure.
Summary
What happened
Heap-based buffer overflow in Samsung Exynos 5G MM message codecs allows remote authenticated users to corrupt baseband memory. NrmmMsgCodec allocates 22 bytes per emergency number but accepts a declared length up to 255 bytes and expands each encoded byte into two output bytes without enforcing that limit. Triggering the flaw requires a malicious mobile network operator or local access; the overwrite causes a baseband crash and limited memory alteration or exposure.
The record
- CVE
- CVE-2023-26072
- Published
- Mar 13, 2023
- Updated
- Mar 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 13, 2023CVE publishedPublication date reported by the CVE source.
- Mar 3, 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.
Public exploit references
- Emergency-number-list proof-of-concept inputproof of concept · demonstrated
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