ChromeWeb browser · Google
CVE-2023-1816
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect security UI in Picture In Picture in Google Chrome prior to 112.0.5615.49 allowed a remote attacker to potentially perform navigation spoofing via a crafted HTML page. (Chromium security severity: Medium)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a UI spoofing vulnerability in Google Chrome's Picture-in-Picture feature where the security UI is incorrect, allowing a remote attacker to potentially perform navigation spoofing via a crafted HTML page. The attacker could display misleading content in the PiP window to trick users about the actual navigation state.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 112.0.5615.49
FedoraOperating system
= 36= 37
Debian LinuxOperating system
= 11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionOpen Chrome, click the three-dot menu, go to Help > About Google Chrome, or navigate to chrome://settings/helpAffected if The version displayed is less than 112.0.5615.49
-
Verify Picture-in-Picture feature statusThe PiP feature is enabled by default in Chrome. To confirm, go to chrome://settings and search for 'Picture-in-Picture' under Privacy and Security settingsAffected if PiP is enabled and Chrome version is vulnerable (below 112.0.5615.49)
-
Check Chrome installation on FedoraRun command: rpm -q google-chrome-stable or dnf list installed | grep chromeAffected if Google Chrome version is installed and is less than 112.0.5615.49
-
Check Chrome installation on DebianRun command: dpkg -l | grep chrome or apt list --installed | grep chromeAffected if Google Chrome version is installed and is less than 112.0.5615.49
You are affected if Google Chrome version is below 112.0.5615.49 and the Picture-in-Picture feature is enabled (which it is by default).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped112.0.5615.49
Update Google Chrome to version 112.0.5615.49 or later to patch this vulnerability.
Chrome 112.0.5615.49 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome to check the current version
- If the version is below 112.0.5615.49, click 'Update Google Chrome' to download and install the latest version
- If automatic updates are disabled, download Chrome 112.0.5615.49 or later from the official Chrome download page (google.com/chrome)
- Restart Google Chrome after the update completes
- Verify the version by returning to Settings > Help > About Google Chrome to confirm version 112.0.5615.49 or later is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1816 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-1816 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data