First published: Fri Mar 17 2023(Updated: )
<p>This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see <a href="https://chromereleases.googleblog.com/2023">Google Chrome Releases</a> for more information.</p>
Credit: Axel Chong chrome-cve-admin@google.com chrome-cve-admin@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
debian/chromium | <=90.0.4430.212-1~deb10u1<=116.0.5845.180-1~deb11u1 | 120.0.6099.129-1~deb11u1 119.0.6045.199-1~deb12u1 120.0.6099.129-1~deb12u1 120.0.6099.129-1 |
Google Chrome | <118.0.5993.70 | |
Debian Debian Linux | =11.0 | |
Debian Debian Linux | =12.0 | |
Microsoft Edge | <118.0.2088.46 | |
Microsoft Edge (Chromium-based) | ||
Google Chrome | <118.0.5993.70 | 118.0.5993.70 |
<118.0.5993.70 | ||
=11.0 | ||
=12.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Found alongside the following vulnerabilities)
The vulnerability ID for this issue is CVE-2023-5483.
The severity of CVE-2023-5483 is medium.
Google Chrome versions prior to 118.0.5993.70 are affected by CVE-2023-5483.
A remote attacker can exploit CVE-2023-5483 by bypassing content security policy via a crafted HTML page in Google Chrome.
Yes, a fix is available for CVE-2023-5483. It is recommended to update Google Chrome to version 118.0.5993.70 or later.