Heap corruption via malformed libxpc strings
Published Feb 27, 2020 · Updated Aug 4, 2024
Memory corruption in Apple libxpc allows local users to corrupt heap memory when an affected device processes a crafted string. Apple identifies inadequate input validation in libxpc string processing as the wrong operation, but has not disclosed the responsible function or parsing logic. Successful exploitation requires local execution and user interaction; public records establish heap corruption but do not identify a reliable code-execution outcome.
Summary
What happened
Memory corruption in Apple libxpc allows local users to corrupt heap memory when an affected device processes a crafted string. Apple identifies inadequate input validation in libxpc string processing as the wrong operation, but has not disclosed the responsible function or parsing logic. Successful exploitation requires local execution and user interaction; public records establish heap corruption but do not identify a reliable code-execution outcome.
The record
- CVE
- CVE-2020-3856
- Published
- Feb 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-787, CWE-20, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <iOS 13.3.1 and iPadOS 13.3.1
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