Physical lock-screen navigation bypass
Published Sep 26, 2022 · Updated May 21, 2025
Incorrect authorization in Google Chrome on ChromeOS before 105.0.5195.52 allows physically proximate attackers to bypass lock-screen navigation controls. The public records do not disclose the faulty lock-screen code path or the authorization check implemented incorrectly. Physical access to a locked ChromeOS device is required, and the established consequence is navigation beyond the lock screen rather than remote browser compromise.
Summary
What happened
Incorrect authorization in Google Chrome on ChromeOS before 105.0.5195.52 allows physically proximate attackers to bypass lock-screen navigation controls. The public records do not disclose the faulty lock-screen code path or the authorization check implemented incorrectly. Physical access to a locked ChromeOS device is required, and the established consequence is navigation beyond the lock screen rather than remote browser compromise.
The record
- CVE
- CVE-2022-3048
- Published
- Sep 26, 2022
- Updated
- May 21, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-863
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2022CVE publishedPublication date reported by the CVE source.
- May 21, 2025Record 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 <105.0.5195.52
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