Unspecified impact via libxml2 bounds-check failure
Published Apr 1, 2020 · Updated Aug 4, 2024
Buffer overflow in libxml2 in affected Apple products allows remote attackers to cause unspecified impact via unspecified vectors. The affected parser code fails to enforce a buffer boundary while processing input; Apple has not published the function, buffer, or input structure involved. Reachability depends on a product feature passing attacker-controlled data to libxml2, and the resulting process behavior remains undisclosed.
Summary
What happened
Buffer overflow in libxml2 in affected Apple products allows remote attackers to cause unspecified impact via unspecified vectors. The affected parser code fails to enforce a buffer boundary while processing input; Apple has not published the function, buffer, or input structure involved. Reachability depends on a product feature passing attacker-controlled data to libxml2, and the resulting process behavior remains undisclosed.
The record
- CVE
- CVE-2020-3911
- 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?
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