Incorrect security UI via crafted fullscreen page
Published Jan 10, 2023 · Updated May 5, 2025
Inappropriate implementation in Google Chrome for Android before 109.0.5414.74 allows remote attackers to display incorrect security UI. Google has not publicly disclosed the Fullscreen API code path or the incorrect operation that produces the security UI state. A user must open a crafted HTML page, after which the page can present misleading security UI in fullscreen mode.
Summary
What happened
Inappropriate implementation in Google Chrome for Android before 109.0.5414.74 allows remote attackers to display incorrect security UI. Google has not publicly disclosed the Fullscreen API code path or the incorrect operation that produces the security UI state. A user must open a crafted HTML page, after which the page can present misleading security UI in fullscreen mode.
The record
- CVE
- CVE-2023-0136
- Published
- Jan 10, 2023
- Updated
- May 5, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2023CVE publishedPublication date reported by the CVE source.
- May 5, 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 <109.0.5414.74
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