Remote service crash via unchecked null pointer
Published Mar 11, 2024 · Updated Mar 27, 2025
A null pointer dereference in GsmSs in Google Android 13 allows remote attackers to crash call-barring handling over a network. ss_SendCallBarringPwdRequiredIndMsg in ss_CallBarring.c dereferences a pointer without first checking it for null. No privileges or user interaction are required, and the documented consequence is availability loss only.
Summary
What happened
A null pointer dereference in GsmSs in Google Android 13 allows remote attackers to crash call-barring handling over a network. ss_SendCallBarringPwdRequiredIndMsg in ss_CallBarring.c dereferences a pointer without first checking it for null. No privileges or user interaction are required, and the documented consequence is availability loss only.
The record
- CVE
- CVE-2024-27229
- Published
- Mar 11, 2024
- Updated
- Mar 27, 2025
- Vendor
- Product
- Android
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13
What conditions does exploitation require?
What is affected?
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