CVE-2017-5030: Google Chromium V8 Memory Corruption
Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2022-06-08.
- CVSS v3.1 (Ubuntu)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 41%
- higher than 98.6% of all CVEs
- Added to CISA KEV
- 2022-06-08
- US federal due date 2022-06-22
- Ubuntu priority
- medium
CVE-2017-5030 explained
CVE-2017-5030 is a memory corruption flaw in the V8 JavaScript engine caused by incorrect handling of complex species. It affects Google Chrome before 57.0.2987.98 on Linux, Windows and Mac and before 57.0.2987.108 on Android. A remote attacker can execute arbitrary code via a crafted HTML page. CISA lists it as a known exploited vulnerability.
Impact
A remote attacker can execute arbitrary code by getting a user to open a crafted HTML page. The attack works over the network, needs no privileges and has low complexity. It does require user interaction, such as visiting a malicious page. Successful exploitation can fully compromise confidentiality, integrity and availability. CISA added this flaw to its Known Exploited Vulnerabilities catalog on 2022-06-08. Ransomware use is listed as unknown.
Who is affected
On Ubuntu 14.04 LTS, chromium-browser is fixed in 58.0.3029.81-0ubuntu0.14.04.1172 and oxide-qt in 1.21.5-0ubuntu0.14.04.1. On Ubuntu 16.04 LTS, chromium-browser is fixed in 57.0.2987.98-0ubuntu0.16.04.1276 and oxide-qt in 1.21.5-0ubuntu0.16.04.1. libv8-3.14 has no fixed version published on Ubuntu 16.04 LTS or Ubuntu 18.04 LTS. Ubuntu 14.04 LTS and 16.04 LTS are end of life. Standard support for Ubuntu 18.04 LTS has ended.
Written with AI from the data on this page and checked against it automatically.
Official description
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.2987.108 for Android 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 Chrome prior to 57.0.2987.98 for Linux, Windows and Mac, and 57.0.2987.108 for AndroidAffectedFixed in
- Google Chrome prior to 57.0.2987.98 for Linux, Windows and Mac, and 57.0.2987.108 for Android
not statedVersion statement as published by the CNA (free text).
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome prior to 57.0.2987.98 for Linux, Windows and Mac, and 57.0.2987.108 for AndroidVersion statement as published by the CNA (free text). |
| not stated |
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·libv8-3.14
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 16.04 LTS·chromium-browser
ESM ended
Fixed: 57.0.2987.98-0ubuntu0.16.04.1276
Ubuntu 16.04 LTS·libv8-3.14
ESM ended
Status: no fixed version published · Ubuntu tracker
Ubuntu 16.04 LTS·oxide-qt
ESM ended
Fixed: 1.21.5-0ubuntu0.16.04.1
Ubuntu 14.04 LTS·chromium-browser
ESM ended
Fixed: 58.0.3029.81-0ubuntu0.14.04.1172
Ubuntu 14.04 LTS·oxide-qt
ESM ended
Fixed: 1.21.5-0ubuntu0.14.04.1
What to do
- Update
chromium-browserandoxide-qtto the fixed versions listed for your release. - Restart the browser and any applications using
oxide-qtso they load the patched code. - Find systems with
libv8-3.14installed and check which applications depend on it. - Plan upgrades of Ubuntu 14.04 LTS and 16.04 LTS systems to a supported release, as these are end of life.
- Plan to move Ubuntu 18.04 LTS systems to a supported release, since standard support has ended.
libv8-3.14 has no fixed version on Ubuntu 16.04 LTS or 18.04 LTS. Ubuntu 16.04 LTS is end of life and should be upgraded. On Ubuntu 18.04 LTS, upgrade to a supported release. Until then, remove libv8-3.14 if nothing needs it. Avoid processing untrusted web content with software that depends on it, and limit network exposure.
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 oxide-qt with the source package from the table above (this CVE affects 3 source packages).
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="oxide-qt"'2. Compare each installed version with the fixed version for your release from the table (releases with a fixed version only)
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=="oxide-qt"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
No fixed version yet on one release
Ubuntu 18.04 LTS: no fixed version of the affected packages yet, so every installed version there is affected. Until a fix is published:
- Follow the vendor's advisory for a mitigation or patch: chromereleases.googleblog.com/2017/03/stable-channel-upda…
- If the server does not need the package, remove it, or replace it with a maintained alternative.
- Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.
This page updates automatically when Ubuntu or Debian publish a fix.
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-125 Out-of-bounds Read
Questions about CVE-2017-5030
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2017-5030 to its Known Exploited Vulnerabilities catalog on 2022-06-08, with a US federal due date of 2022-06-22. The required action is to apply updates per vendor instructions. Known ransomware use is listed as unknown.
- Does a user need to do anything for an attack to succeed?
- Yes. User interaction is required. The attacker must get a user to open a crafted HTML page. No privileges are needed, and the attack can come over the network.
- Why is libv8-3.14 still listed without a fix?
- No fixed version of
libv8-3.14has been published for Ubuntu 16.04 LTS or Ubuntu 18.04 LTS. Ubuntu 16.04 LTS is end of life. Standard support for Ubuntu 18.04 LTS has ended. Upgrading to a supported release is the recommended path.
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-22. Always confirm with the vendor's or distribution's advisory before patching.