VulnerabilityPublished 23 Jan 2024Updated 30 May 2025

CVE-2024-0814: Google Chrome · Incorrect Security UI

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 121.0.6167.85 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 121.0.6167.85

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade the Ubuntu ubuntu/google-chrome package to 121.0.6167.85.

Affected software

Product	Affected	Fixed in
Ubuntuubuntu/google-chrome`pkg:deb/ubuntu/google-chrome`Other threats	Affected <121.0.6167.85	Fixed in 121.0.6167.85

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should ensure that all instances of Google Chrome are updated to version 121.0.6167.85 or later, where this vulnerability is fixed. Automated patch management systems should be employed to enforce timely updates across all user endpoints. Additionally, organizations should educate users about the risks of interacting with unexpected payment prompts and encourage verification of payment requests through out-of-band channels. Web filtering solutions can be configured to block or flag suspicious or untrusted websites that may host malicious HTML pages exploiting this vulnerability. For critical financial applications, consider implementing multi-factor authentication and transaction verification mechanisms independent of browser UI cues to reduce reliance on browser security indicators. Security teams should monitor for phishing campaigns that leverage spoofed payment UIs and incorporate this vulnerability into threat intelligence feeds. Finally, organizations should review their incident response plans to address potential fraud incidents stemming from UI spoofing attacks.

Description

Incorrect 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)

Impact

For European organizations, this vulnerability poses a significant risk especially to businesses and users involved in online payments, e-commerce, and financial services. Attackers could exploit this flaw to conduct phishing attacks that appear to originate from legitimate payment prompts, potentially leading to fraudulent transactions or theft of payment credentials. This could result in financial losses, reputational damage, and regulatory scrutiny under GDPR and PSD2 regulations that mandate strong security controls for payment processing. Organizations relying on Chrome for their web-based payment interfaces or customer interactions may see increased risk of customer fraud and trust erosion. Additionally, employees using vulnerable Chrome versions could be targeted to gain unauthorized access to corporate financial resources or sensitive transaction data. Although the vulnerability does not directly compromise confidentiality or availability, the integrity impact is critical in the context of payments, where trust in UI authenticity is paramount. The medium severity rating reflects the need for prompt patching and user awareness to mitigate social engineering risks.

CWE-346Origin Validation Error (opens in a new tab)
Class weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not properly verify that the source of data or communication is valid.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V14.5.2 (opens in a new tab)
V14.5.3 (opens in a new tab)
V1.4.4 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cache Poisoning (opens in a new tab)
DNS Cache Poisoning (opens in a new tab)
Exploit Script-Based APIs (opens in a new tab)
Application API Message Manipulation via Man-in-the-Middle (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 19:43 UTC

WeaknessesCWE-346

Technical details

References

Community reviews

Related threats