Physical policy bypass via ADB wireless debugging
Published Dec 20, 2023 · Updated Aug 2, 2024
Insufficient policy enforcement in Chrome on ChromeOS before 114.0.5735.90 allows physically proximate attackers to bypass device policies. The affected ADB wireless-debugging path fails to preserve the intended policy restriction; Google has not disclosed the specific check or code path. Physical access to an affected ChromeOS device is required, and successful exploitation defeats administrator-enforced device restrictions.
Summary
What happened
Insufficient policy enforcement in Chrome on ChromeOS before 114.0.5735.90 allows physically proximate attackers to bypass device policies. The affected ADB wireless-debugging path fails to preserve the intended policy restriction; Google has not disclosed the specific check or code path. Physical access to an affected ChromeOS device is required, and successful exploitation defeats administrator-enforced device restrictions.
The record
- CVE
- CVE-2023-3742
- Published
- Dec 20, 2023
- Updated
- Aug 2, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- Unavailable
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 20, 2023CVE 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=114.0.5735.90 <114.0.5735.90
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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