CVE-2023-6512VulnerabilityPublished 6 Dec 2023Updated 28 May 2025

CVE-2023-6512: Google Chrome · Inappropriate implementation

Affects Google ChromeSource CVE Database V5

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

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

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

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

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 6 Dec 2023
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 2026-10-25.

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 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 debian/chrome to 120.0.6099.62.

Affected software

Product	Affected	Fixed in
Debiandebian/chrome`pkg:deb/debian/chrome`Other threats	Affected <120.0.6099.62	Fixed in 120.0.6099.62

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 prioritize updating Google Chrome to version 120.0.6099.62 or later as soon as it becomes available to ensure the vulnerability is patched. In the interim, organizations can implement browser security policies that restrict iframe usage from untrusted sources, such as Content Security Policy (CSP) directives limiting frame-ancestors and frame-src to trusted domains only. User training should emphasize caution when interacting with unexpected context menus or dialog boxes, especially within embedded frames. Security teams should monitor for phishing campaigns that may leverage this vulnerability for social engineering. Deploying endpoint protection solutions with web filtering capabilities can help block access to malicious crafted HTML pages. Additionally, organizations can consider browser hardening techniques, such as disabling unnecessary plugins or extensions that might increase attack surface. Regular vulnerability scanning and penetration testing focusing on browser UI spoofing scenarios can help identify residual risks. Finally, maintaining an incident response plan that includes browser-based attack vectors will improve readiness against exploitation attempts.

Description

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

Impact

For European organizations, this vulnerability poses a moderate risk primarily through social engineering and phishing campaigns. Attackers exploiting this flaw could craft web pages that display deceptive context menus within iframes, potentially tricking employees into executing malicious actions, such as clicking on malicious links or granting permissions unknowingly. This could lead to further compromise of internal systems or data leakage. Since Google Chrome is widely used across European enterprises and public sector organizations, the attack surface is significant. The integrity of the browser UI being compromised can reduce user confidence and increase susceptibility to targeted attacks. However, the lack of impact on confidentiality and availability limits the direct damage to system resources or data theft solely from this vulnerability. The requirement for user interaction means that user awareness and training remain important factors in mitigating risk. Additionally, sectors with high reliance on secure web interactions, such as finance, healthcare, and government, may be more sensitive to such UI spoofing attacks as they can facilitate more complex multi-stage attacks.

CWE-838Inappropriate Encoding for Output Context (opens in a new tab)
Base weakness
The product uses or specifies an encoding when generating output to a downstream component, but the specified encoding is not the same as the encoding that is expected by the downstream component.
Implementation · Output Encoding
Use context-aware encoding. That is, understand which encoding is being used by the downstream component, and ensure that this encoding is used. If an encoding can be specified, do so, instead of assuming that the default encoding is the same as the default being assumed by the downstream component.
Architecture and Design · Output Encoding
Where possible, use communications protocols or data formats that provide strict boundaries between control and data. If this is not feasible, ensure that the protocols or formats allow the communicating components to explicitly state which encoding/decoding method is being used.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Content Security Policy (opens in a new tab)
OWASP ASVS 4.0.3
V14.4.6 (opens in a new tab)
V14.4.4 (opens in a new tab)
V14.4.2 (opens in a new tab)
Attack patterns
Generic Cross-Browser Cross-Domain Theft (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 7 Jul 2025, 08:24 UTC

WeaknessesCWE-838

Technical details

References

Community reviews

Related threats