CVE-2022-2618: Insufficient validation of untrusted input in Internals

Reference Links

• https://chromereleases.googleblog.com/2022/08/stable-channel-update-for-desktop.html (Advisory)
• https://crbug.com/1308422
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T4NMJURTG5RO3TGD7ZMIQ6Z4ZZ3SAVYE/
• https://security.gentoo.org/glsa/202208-35
• https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/T4NMJURTG5RO3TGD7ZMIQ6Z4ZZ3SAVYE/

Parent vulnerabilities

(Appears in the following advisories)

• 849835485002254358

Peer vulnerabilities

(Found alongside the following vulnerabilities)

• CVE-2022-2603
• CVE-2022-2604
• CVE-2022-2605
• CVE-2022-2606
• CVE-2022-2607
• CVE-2022-2608
• CVE-2022-2609
• CVE-2022-2742
• CVE-2022-2743
• CVE-2022-2610
• CVE-2022-2611
• CVE-2022-2612
• CVE-2022-2613
• CVE-2022-2614
• CVE-2022-4914
• CVE-2022-2615
• CVE-2022-2616
• CVE-2022-2617
• CVE-2022-2619
• CVE-2022-2620
• CVE-2022-2621
• CVE-2022-2622
• CVE-2022-2623
• CVE-2022-2624

Frequently Asked Questions

• What is the severity of CVE-2022-2618?

  CVE-2022-2618 has a moderate severity rating, indicating it poses a significant risk if exploited.

• How do I fix CVE-2022-2618?

  To fix CVE-2022-2618, users should update Google Chrome to version 104.0.5112.79 or later.

• What are the effects of CVE-2022-2618?

  CVE-2022-2618 can allow remote attackers to bypass download restrictions through malicious files.

• Is CVE-2022-2618 specific to any operating system?

  CVE-2022-2618 affects Google Chrome across multiple operating systems, including Fedora.

• Can I still be vulnerable to CVE-2022-2618 if I am using an updated version of Chrome?

  No, if you are using Google Chrome version 104.0.5112.79 or later, you are not vulnerable to CVE-2022-2618.