CVE-2018-17480: Google Chromium V8 Out-of-Bounds Write
Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2022-06-08.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 36%
- higher than 98.4% of all CVEs
- Added to CISA KEV
- 2022-06-08
- US federal due date 2022-06-22
- Ubuntu priority
- medium
CVE-2018-17480 explained
CVE-2018-17480 is an out-of-bounds write in the V8 JavaScript engine used by Google Chrome before 71.0.3578.80. User-supplied JavaScript running during array deserialization can corrupt memory. A crafted HTML page can lead to arbitrary code execution inside the browser sandbox. CISA lists it as a known exploited vulnerability, so unpatched browsers are at real risk.
Impact
A remote attacker can execute arbitrary code inside the browser sandbox. No privileges are needed and the attack is low in complexity. It works over the network, but a user must open a crafted HTML page. Successful exploitation can fully compromise confidentiality, integrity and availability within the affected browser process. CISA added the flaw to its Known Exploited Vulnerabilities catalog on 2022-06-08. Use in ransomware campaigns is listed as unknown.
Who is affected
The affected Ubuntu source package is chromium-browser. Ubuntu 16.04 LTS has a fix in 71.0.3578.80-0ubuntu0.16.04.1 from the standard archive, but this release is end of life. Ubuntu 18.04 LTS has a fix in 71.0.3578.80-0ubuntu0.18.04.1 from the standard archive. Standard support for 18.04 has ended, and further fixes there come only with Ubuntu Pro (ESM). The facts list no Debian releases.
Written with AI from the data on this page and checked against it automatically.
Official description
Execution of user supplied Javascript during array deserialization leading to an out of bounds write in V8 in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to execute arbitrary code inside a sandbox 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
- < 71.0.3578.80
- 71.0.3578.80
| 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: 71.0.3578.80-0ubuntu0.18.04.1
Ubuntu 16.04 LTS·chromium-browser
ESM ended
Fixed: 71.0.3578.80-0ubuntu0.16.04.1
What to do
- Update
chromium-browserto the fixed version for your release, or a later one. - Restart all running Chromium browser instances so the patched code is loaded.
- Plan an upgrade of Ubuntu 16.04 LTS systems to a supported release, since it is end of life.
- On Ubuntu 18.04 LTS, enable Ubuntu Pro (ESM) to keep receiving future security fixes, or upgrade to a supported release.
- Verify the installed package version on every system that runs Chromium.
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-787 Out-of-bounds Write
Questions about CVE-2018-17480
- Is this vulnerability exploited in the wild?
- Yes. CISA added CVE-2018-17480 to its Known Exploited Vulnerabilities catalog on 2022-06-08. The required action is to apply updates per vendor instructions.
- Does a user need to do anything for an attack to succeed?
- Yes. User interaction is required. The victim must open a crafted HTML page in a vulnerable browser. No privileges are needed.
- Do I need to reboot after updating?
- A reboot is not required. You must restart Chromium, because running browser processes 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
Other advisories
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.