Navigation restriction bypass via Pointer Lock
Published Apr 5, 2022 · Updated Aug 2, 2024
Improper Pointer Lock implementation in Google Chrome before 98.0.4758.80 on Windows allows remote attackers to bypass navigation restrictions. Google identifies Pointer Lock as the affected component but has not publicly disclosed the implementation locus or incorrect operation performed on crafted HTML. Exploitation requires a Windows user to open and interact with a crafted page, after which the page circumvents browser navigation controls; no code execution or service interruption is reported.
Summary
What happened
Improper Pointer Lock implementation in Google Chrome before 98.0.4758.80 on Windows allows remote attackers to bypass navigation restrictions. Google identifies Pointer Lock as the affected component but has not publicly disclosed the implementation locus or incorrect operation performed on crafted HTML. Exploitation requires a Windows user to open and interact with a crafted page, after which the page circumvents browser navigation controls; no code execution or service interruption is reported.
The record
- CVE
- CVE-2022-0467
- Published
- Apr 5, 2022
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 5, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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 <98.0.4758.80
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
No sourced classifications are available.
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