CVE-2023-4232: ofono · Memory Buffer Overflow
Affects ofonoSource CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Monitor vendor advisories closely and apply official patches or updates for ofono as soon as they become available.
- Implement strict network segmentation to isolate modems and telephony stacks from critical internal networks, limiting attacker lateral movement.
- Restrict access to modems and cellular interfaces to trusted management systems only, using strong authentication and access controls.
- Deploy anomaly detection systems to monitor SMS traffic for unusual or malformed messages that could indicate exploitation attempts.
- Where possible, disable or limit SMS status report processing if not required by the operational environment.
- Conduct regular security assessments of embedded devices and telephony infrastructure to identify and remediate outdated or vulnerable software components.
- Collaborate with telecom providers to ensure base stations and network elements are secured against compromise, reducing attack surface from malicious base stations.
Description
A flaw was found in ofono, an Open Source Telephony on Linux. A stack overflow bug is triggered within the decode_status_report() function during the SMS decoding. It is assumed that the attack scenario is accessible from a compromised modem, a malicious base station, or just SMS. There is a bound check for this memcpy length in decode_submit(), but it was forgotten in decode_status_report().