Process-memory disclosure via appcache policy bypass
Published Mar 9, 2021 · Updated Aug 3, 2024
Insufficient policy enforcement in Google Chrome before 89.0.4389.72 allows remote attackers to read process memory via crafted HTML. The appcache component processes attacker-controlled HTML without enforcing the policy boundary that protects process memory; the affected code path is undisclosed. A user must open the crafted page, and the documented consequence is disclosure of potentially sensitive memory rather than data modification or service interruption.
Summary
What happened
Insufficient policy enforcement in Google Chrome before 89.0.4389.72 allows remote attackers to read process memory via crafted HTML. The appcache component processes attacker-controlled HTML without enforcing the policy boundary that protects process memory; the affected code path is undisclosed. A user must open the crafted page, and the documented consequence is disclosure of potentially sensitive memory rather than data modification or service interruption.
The record
- CVE
- CVE-2021-21168
- Published
- Mar 9, 2021
- Updated
- Aug 3, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 9, 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 <89.0.4389.72
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