CVE-2020-6572: Google Chrome Media Use-After-Free
Google Chrome Media · listed in the CISA catalog of actively exploited vulnerabilities since 2022-01-10.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 11%
- higher than 95.8% of all CVEs
- Added to CISA KEV
- 2022-01-10
- US federal due date 2022-07-10
- Ubuntu priority
- medium
CVE-2020-6572 explained
CVE-2020-6572 is a use-after-free flaw in the Media component of Google Chrome before 81.0.4044.92. A remote attacker can execute arbitrary code when a user opens a crafted HTML page. CISA lists it as known to be exploited, so affected chromium-browser packages should be updated promptly.
Impact
An attacker who gets a user to visit a crafted HTML page can run arbitrary code over the network. No privileges are needed and attack complexity is low, but user interaction is required. Successful exploitation has high impact on confidentiality, integrity and availability within the browser's context. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-01-10. Ransomware use is unknown.
Who is affected
The affected source package is chromium-browser. On Ubuntu 16.04 LTS, a fix is available as 89.0.4389.82-0ubuntu0.16.04.1. That release is end of life. On Ubuntu 18.04 LTS, the fix is 89.0.4389.82-0ubuntu0.18.04.1 in the standard archive. Standard support for 18.04 has ended, and further fixes are only available with Ubuntu Pro (ESM). Upstream, Google Chrome versions before 81.0.4044.92 are affected.
Written with AI from the data on this page and checked against it automatically.
Official description
Use after free in Media in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to execute arbitrary code via a crafted HTML page.
CISA required action: Apply updates per vendor instructions.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 81.0.4044.92
- 81.0.4044.92
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 18.04 LTS·chromium-browser
Fixed: 89.0.4389.82-0ubuntu0.18.04.1
Ubuntu 16.04 LTS·chromium-browser
ESM ended
Fixed: 89.0.4389.82-0ubuntu0.16.04.1
What to do
- Update
chromium-browserto89.0.4389.82-0ubuntu0.18.04.1on Ubuntu 18.04 LTS or89.0.4389.82-0ubuntu0.16.04.1on Ubuntu 16.04 LTS. - Close and restart all running browser instances so the patched code is loaded.
- Plan an upgrade of Ubuntu 16.04 LTS systems to a supported release, because it is end of life.
- For Ubuntu 18.04 LTS, enable Ubuntu Pro (ESM) or upgrade to keep receiving later security fixes.
- Follow the distribution advisory and CISA's required action: apply updates per vendor instructions.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace chromium-browser with the source package from the table above.
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium-browser"'2. Compare each installed version with the fixed version for your release from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium-browser"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-416 Use After Free
Questions about CVE-2020-6572
- Is this vulnerability exploited in the wild?
- Yes. CISA added CVE-2020-6572 to its Known Exploited Vulnerabilities catalog on 2022-01-10, with a US federal due date of 2022-07-10. Whether it has been used in ransomware campaigns is unknown.
- Does an attacker need access to my system?
- No. The attack works over the network and needs no privileges. However, a user must open a crafted HTML page in the vulnerable browser.
- Is updating the package enough?
- Install the fixed
chromium-browserversion, then restart every open browser instance. Running browsers keep using the old, vulnerable code until they are restarted.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.