CVE-2023-6512: Inappropriate implementation in Web Browser UI
Chromium: CVE-2023-6512 Inappropriate implementation in Web Browser UI
Other sources
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)
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Google Chrome (Trace Event)to a version that resolves this vulnerability.Fixed in 120.0.6099.62 - Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 150.0.7871.100-1~deb12u1Fixed in 156.0.8078.79-1~deb12u1Fixed in 150.0.7871.181-1~deb13u1Fixed in 156.0.8078.79-1~deb13u1Fixed in 156.0.8078.79-1 - Upgrade
Upgrade
Chromiumto a version that resolves this vulnerability.Fixed in 120.0.6099.62
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is CVE-2023-6512?
CVE-2023-6512 is a vulnerability in Google Chrome where inappropriate implementation in Web Browser UI allows a remote attacker to potentially spoof the contents of an iframe dialog context menu via a crafted HTML page.
What is the severity of CVE-2023-6512?
The severity of CVE-2023-6512 is classified as Low.
Which software is affected by CVE-2023-6512?
Microsoft Edge and Microsoft Edge (Chromium-based) versions prior to 120.0.2210.61 are affected by CVE-2023-6512.
How can I fix CVE-2023-6512?
To fix CVE-2023-6512, update your Microsoft Edge or Microsoft Edge (Chromium-based) to version 120.0.2210.61 or above. Refer to the Microsoft Edge security updates page for more information.
Where can I get more information about CVE-2023-6512?
You can find more information about CVE-2023-6512 in the Google Chrome release blog and the Microsoft Security Response Center website.