ChromeWeb browser · Google
CVE-2024-0814
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 Payments in Google Chrome prior to 121.0.6167.85 allowed a remote attacker to potentially spoof security UI 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 Payments component. A remote attacker can craft a malicious HTML page that displays deceptive security UI, potentially tricking users into believing they're on a legitimate payment interface. This could facilitate phishing attacks but does not directly enable code execution or data exfiltration.
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
< 121.0.6167.85
FedoraOperating system
= 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
- 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 installed Google Chrome versionOpen chrome://settings/help or run 'google-chrome --version' from command lineAffected if Version number is less than 121.0.6167.85
-
Check Chrome package version on FedoraRun 'rpm -q google-chrome' on Fedora 38 or 39 systemsAffected if Package version is present and lower than 121.0.6167.85-1
-
Verify Payments component is in useThe Payments component is built into Chrome - no configuration needed. Check if Chrome's payment autofill or payment methods are accessible at chrome://settings/paymentsAffected if The browser has payment features enabled (default state) and version is vulnerable
A user is affected if their Google Chrome version is below 121.0.6167.85, regardless of operating system, since the UI spoofing flaw exists in the built-in Payments component itself.
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 · scoped121.0.6167.85
Update Google Chrome to version 121.0.6167.85 or later. In enterprise environments, verify patch deployment through existing endpoint management tools.
Chrome 121.0.6167.85 or later (or google-chrome-stable/chromium packages in Fedora repos updated to the fixed version)
- For Chrome users: Open Chrome, click the three-dot menu in the top-right, go to Help > About Google Chrome, and click 'Update Google Chrome' to install version 121.0.6167.85 or later.
- For Fedora systems: Run 'sudo dnf update google-chrome-stable' or 'sudo dnf update chromium' to apply the security patch.
- Restart the browser after the update completes.
- Verify the installed version by going to chrome://settings/help - it should show 121.0.6167.85 or higher.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0814 — 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-2024-0814 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