Heap corruption via crafted-file double free
Published Sep 8, 2021 · Updated Aug 3, 2024
Double free in libxslt across affected Apple operating systems allows attackers to corrupt heap memory by processing a crafted file. The libxslt parser releases the same heap allocation twice while handling malicious file content, although Apple has not disclosed the affected function or parsing path. A user or application must cause the targeted device to process the file; Apple reports heap corruption, not demonstrated code execution.
Summary
What happened
Double free in libxslt across affected Apple operating systems allows attackers to corrupt heap memory by processing a crafted file. The libxslt parser releases the same heap allocation twice while handling malicious file content, although Apple has not disclosed the affected function or parsing path. A user or application must cause the targeted device to process the file; Apple reports heap corruption, not demonstrated code execution.
The record
- CVE
- CVE-2021-1875
- Published
- Sep 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-415, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <14.5
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.
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