Memory corruption via unchecked libxml2 input size
Published Apr 1, 2020 · Updated Aug 4, 2024
A libxml2 buffer overflow in affected Apple platforms and Windows clients allows attackers to corrupt memory through oversized input. Apple states that improved size validation corrected the flaw but does not identify the libxml2 function, field, or parsing operation that accepts the untrusted size. The disclosure does not specify how input reaches the component or whether corruption yields a crash, data access, or code execution.
Summary
What happened
A libxml2 buffer overflow in affected Apple platforms and Windows clients allows attackers to corrupt memory through oversized input. Apple states that improved size validation corrected the flaw but does not identify the libxml2 function, field, or parsing operation that accepts the untrusted size. The disclosure does not specify how input reaches the component or whether corruption yields a crash, data access, or code execution.
The record
- CVE
- CVE-2020-3910
- Published
- Apr 1, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 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.4 and iPadOS 13.4
What conditions does exploitation require?
What is affected?
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