CVE-2024-1669: Out of bounds memory access in Blink

Reference Links

• https://chromereleases.googleblog.com/2024/02/stable-channel-update-for-desktop_20.html (Advisory)
• https://issues.chromium.org/issues/41495060
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QDCMYQ3J45NHQ4EJREM3BJNNKB5BK4Y7/
• https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-1669 (Advisory)
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PWWBMVQTSERVBXSXCZVUKIMEDNQUQ7O3/

Parent vulnerabilities

(Appears in the following advisories)

• 1133025810642778744

Peer vulnerabilities

(Found alongside the following vulnerabilities)

• CVE-2024-1670
• CVE-2024-5500
• CVE-2024-3168
• CVE-2024-1671
• CVE-2024-1672
• CVE-2024-1673
• CVE-2024-1674
• CVE-2024-1675
• CVE-2024-3171
• CVE-2024-1676

Frequently Asked Questions

• What is the severity of CVE-2024-1669?

  CVE-2024-1669 has a critical severity rating due to the potential for exploitation through out-of-bounds memory access.

• How do I fix CVE-2024-1669?

  To fix CVE-2024-1669, update Google Chrome to version 122.0.6261.57 or later, or apply the necessary updates for Microsoft Edge based on the current version.

• Which software is affected by CVE-2024-1669?

  CVE-2024-1669 affects Google Chrome versions prior to 122.0.6261.57 and Microsoft Edge (Chromium-based) that relies on Chromium.

• Is there a workaround for CVE-2024-1669?

  There are no known workarounds for CVE-2024-1669, so users are advised to apply the latest updates.

• Where can I find more details about CVE-2024-1669?

  For more details on CVE-2024-1669, refer to the security announcements from Google and Microsoft regarding their respective browser updates.