Secure-context bypass via opaque-origin trust
Published Feb 27, 2020 · Updated Aug 4, 2024
WebKit Page Loading in affected Apple products allows remote attackers to create a secure context from attacker-controlled HTTP content. Safari treats every opaque-origin document as trustworthy and checks parent security without correctly traversing the opener chain. A user must visit attacker-controlled HTTP content; the flaw unlocks secure-context-only browser APIs rather than arbitrary code execution by itself.
Summary
What happened
WebKit Page Loading in affected Apple products allows remote attackers to create a secure context from attacker-controlled HTTP content. Safari treats every opaque-origin document as trustworthy and checks parent security without correctly traversing the opener chain. A user must visit attacker-controlled HTTP content; the flaw unlocks secure-context-only browser APIs rather than arbitrary code execution by itself.
The record
- CVE
- CVE-2020-3865
- Published
- Feb 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Apple
- Product
- iOS
- Classifications
- CWE-787, T1189
- Attack vector
- network
- 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.
Public exploit references
- Webcam Hacking technical walkthroughproof of concept · demonstrated
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