ChromeWeb browser · Google
CVE-2023-4764
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 BFCache in Google Chrome prior to 116.0.5845.179 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page. (Chromium security severity: High)
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 confidenceA security UI vulnerability in Chrome's Back-Forward Cache (BFCache) allows a remote attacker to spoof the contents of the Omnibox (URL bar) through a crafted HTML page. When users navigate away from a page and back, the cached page can display a fake URL in the address bar while the user is actually on a different (potentially malicious) page. This bypasses the user's ability to verify the legitimacy of the site they're visiting.
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
< 116.0.5845.179
Debian LinuxOperating system
= 11.0= 12.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.
-
Identify installed Chrome browserOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' or 'chrome --version' in terminalAffected if Google Chrome is installed on the system
-
Verify Chrome version against affected rangeCompare the installed version number to 116.0.5845.179 - any version lower than this (e.g., 116.0.5845.110, 115.x.x.x) is affectedAffected if Installed version is less than 116.0.5845.179
-
Confirm BFCache is in useThe vulnerability affects any user who navigates web pages - BFCache is enabled by default in Chrome; no manual configuration needed to be vulnerableAffected if Browser uses Back-Forward Cache for page navigation (default behavior)
User is affected if running Google Chrome version lower than 116.0.5845.179 on Debian Linux 11.0 or 12.0, where the BFCache feature is enabled by default and allows page restoration to potentially display spoofed URLs in the Omnibox.
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 · scoped116.0.5845.179
Users should update Google Chrome to version 116.0.5845.179 or later. Organizations may need to deploy browser updates through their endpoint management systems.
Chrome 116.0.5845.179 or later (Debian: apply security updates)
- Update Google Chrome to version 116.0.5845.179 or later by navigating to chrome://settings/help and clicking 'Update Google Chrome'
- On Debian Linux 11.0 and 12.0, apply available security updates for the chromium package via: apt update && apt upgrade chromium (or apt update && apt install --only-upgrade chromium)
- Restart the browser after updating to ensure the security fix is fully applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4764 — 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-4764 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