Sandbox escape via improper iframe handling
Published Jul 16, 2024 · Updated Nov 21, 2024
Improper iframe handling in Google Chrome before 77.0.3865.75 allows remote attackers to escape the sandbox via crafted HTML. Google has not published which iframe operation mishandles the page or how the sandbox boundary is crossed. Exploitation requires loading attacker-controlled HTML; the disclosed consequence is escape from the browser sandbox.
Summary
What happened
Improper iframe handling in Google Chrome before 77.0.3865.75 allows remote attackers to escape the sandbox via crafted HTML. Google has not published which iframe operation mishandles the page or how the sandbox boundary is crossed. Exploitation requires loading attacker-controlled HTML; the disclosed consequence is escape from the browser sandbox.
The record
- CVE
- CVE-2019-25154
- Published
- Jul 16, 2024
- Updated
- Nov 21, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 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=77.0.3865.75 <77.0.3865.75
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