Debian LinuxOperating system · Debian
CVE-2023-6512
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 · uneditedInappropriate implementation in Web Browser UI in Google Chrome prior to 120.0.6099.62 allowed a remote attacker to potentially spoof the contents of an iframe dialog context menu via a crafted HTML page. (Chromium security severity: Low)
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 confidenceGoogle Chrome prior to version 120.0.6099.62 had an inappropriate implementation in the Web Browser UI that allowed a remote attacker to spoof the contents of an iframe dialog context menu through a crafted HTML page, potentially misleading users about the origin of the context menu.
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
Debian LinuxOperating system
= 11.0= 12.0
FedoraOperating system
= 38= 39
ChromeWeb browser
< 120.0.6099.62CVSS 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 versionNavigate to chrome://settings/help or use the menu: Help > About Google Chrome. The version number is displayed at the top of the page.Affected if Version is earlier than 120.0.6099.62 (e.g., 119.x.x.x or earlier)
-
Check Debian system Chrome package versionRun command: dpkg -l | grep chrome or apt list --installed | grep chromeAffected if Package version is less than 120.0.6099.62-1 or the package is not present (meaning Chrome may have been installed manually without using the system package)
You are affected if Google Chrome (whether installed via system package or manually) reports a version number lower than 120.0.6099.62.
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 · scoped120.0.6099.62
Update Google Chrome to version 120.0.6099.62 or later. No code-level changes required; this is a client-side browser update.
Chrome 120.0.6099.62 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome to check the current version
- Verify the installed version is 120.0.6099.62 or later; if not, the browser should automatically update
- If automatic update does not occur, download the latest Chrome stable build from the official Chrome download page (google.com/chrome)
- Install the updated Chrome version
- Restart the browser to apply the update
- For Linux distributions (Debian 11/12, Fedora 38/39), alternatively run: sudo apt update && sudo apt upgrade google-chrome-stable (Debian) or sudo dnf update google-chrome (Fedora)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
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-6512 — 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-6512 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