ChromeWeb browser · Google
CVE-2023-5480
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 Payments in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to bypass XSS preventions via a malicious file. (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 · moderate confidenceInappropriate implementation in Google Chrome's Payments component prior to version 119.0.6045.105 allowed a remote attacker to bypass Cross-Site Scripting (XSS) prevention mechanisms via a malicious file. This could enable injection of arbitrary script code into the Payments context.
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
< 119.0.6045.105
Debian LinuxOperating system
= 11.0= 12.0
FedoraOperating system
= 37= 38= 39CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed Chrome version on Windows or MacOpen Chrome, click the three-dot menu, select Help, then About Google Chrome. The version number is displayed on that page.Affected if The displayed version is earlier than 119.0.6045.105
-
Check installed Chrome version on Debian LinuxOpen a terminal and run: dpkg -l | grep chrome or apt list --installed 2>/dev/null | grep chromeAffected if The listed Chrome version is earlier than 119.0.6045.105
-
Check installed Chrome version on Fedora LinuxOpen a terminal and run: rpm -qa | grep chromeAffected if The listed Chrome version is earlier than 119.0.6045.105
-
Verify Chrome is being usedConfirm that Google Chrome is the primary browser in use on the system. This vulnerability affects Chrome specifically, not other browsers.Affected if Google Chrome is installed and in use with a version below 119.0.6045.105
If Google Chrome version is lower than 119.0.6045.105 on any operating system, the Payments component is vulnerable to XSS prevention bypass.
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 · scoped119.0.6045.105
Update Google Chrome to version 119.0.6045.105 or later. Organizations should ensure end-user browsers are updated through their standard patch management processes.
Chrome 119.0.6045.105 or later
- Check current Google Chrome version by navigating to chrome://settings/help or running `google-chrome --version` in terminal
- Download and install Google Chrome version 119.0.6045.105 or later from the official Google Chrome website (google.com/chrome)
- For Linux distributions, alternatively apply distribution security updates (e.g., `sudo dnf update` for Fedora or `sudo apt update && sudo apt upgrade` for Debian)
- Restart Chrome after installation to ensure the update takes effect
- Verify the version has been updated to 119.0.6045.105 or later via chrome://settings/help
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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-5480 — 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-5480 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