CVE-2020-16001: Use after free in media

Reference Links

• https://chromereleases.googleblog.com/2020/10/stable-channel-update-for-desktop_20.html (Advisory)
• http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00016.html
• https://crbug.com/1135018
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/24QFL4C3AZKMFVL7LVSYMU2DNE5VVUGS/
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4GWCWNHTTYOH6HSFUXPGPBB6J6JYZHZE/
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SC3U3H6AISVZB5PLZLLNF4HMQ4UFFL7M/
• https://security.gentoo.org/glsa/202101-30
• https://www.debian.org/security/2021/dsa-4824
• https://security-tracker.debian.org/tracker/CVE-2020-16001

Parent vulnerabilities

(Appears in the following advisories)

• 164021554802225166

Peer vulnerabilities

(Found alongside the following vulnerabilities)

• CVE-2020-16000
• CVE-2020-16002
• CVE-2020-15999
• CVE-2020-16003

Frequently Asked Questions

• What is CVE-2020-16001?

  CVE-2020-16001 is a vulnerability in Google Chrome that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.

• What software is affected by CVE-2020-16001?

  CVE-2020-16001 affects Google Chrome versions prior to 86.0.4240.111, Debian Linux 10.0, openSUSE Backports SLE 15.0-sp2, and Fedoraproject Fedora 31, 32, and 33.

• What is the severity of CVE-2020-16001?

  CVE-2020-16001 has a severity score of 8.8, which is considered high.

• How can I fix CVE-2020-16001?

  To fix CVE-2020-16001, you should update your Google Chrome to version 86.0.4240.111 or later.

• Where can I find more information about CVE-2020-16001?

  You can find more information about CVE-2020-16001 at the following references: http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00016.html, https://chromereleases.googleblog.com/2020/10/stable-channel-update-for-desktop_20.html, https://crbug.com/1135018