Local memory corruption via unvalidated native handles
Published Jun 7, 2024 · Updated Oct 29, 2024
Out-of-bounds write in Samsung Exynos 2200, Exynos 1480, and Exynos 2400 allows local users to corrupt memory via native handles. The mobile processor fails to validate native handles before using them in a memory operation, permitting a handle to drive a write beyond the intended buffer. Local access is required; public details do not identify the affected component or establish code execution, privilege escalation, or disclosure.
Summary
What happened
Out-of-bounds write in Samsung Exynos 2200, Exynos 1480, and Exynos 2400 allows local users to corrupt memory via native handles. The mobile processor fails to validate native handles before using them in a memory operation, permitting a handle to drive a write beyond the intended buffer. Local access is required; public details do not identify the affected component or establish code execution, privilege escalation, or disclosure.
The record
- CVE
- CVE-2024-31958
- Published
- Jun 7, 2024
- Updated
- Oct 29, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-354
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 7, 2024CVE publishedPublication date reported by the CVE source.
- Oct 29, 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.
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