Memory corruption via unchecked Call Control length
Published Dec 2, 2024 · Updated Dec 3, 2024
Out-of-bounds write in Samsung Exynos baseband software allows remote attackers to corrupt memory via crafted Call Control input. The baseband trusts the length specified by the CC (Call Control) layer without adequately checking it before writing to a destination buffer. The network path requires no authentication or user interaction, but public records do not disclose the crafted message format or any resulting code-execution capability.
Summary
What happened
Out-of-bounds write in Samsung Exynos baseband software allows remote attackers to corrupt memory via crafted Call Control input. The baseband trusts the length specified by the CC (Call Control) layer without adequately checking it before writing to a destination buffer. The network path requires no authentication or user interaction, but public records do not disclose the crafted message format or any resulting code-execution capability.
The record
- CVE
- CVE-2024-39890
- Published
- Dec 2, 2024
- Updated
- Dec 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 2, 2024CVE publishedPublication date reported by the CVE source.
- Dec 3, 2024Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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