Skip to content
Server Security Center
KEVhigh8.8

CVE-2017-5070: Google Chromium V8 Type Confusion

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)
32%
higher than 98.3% of all CVEs
Added to CISA KEV
2022-06-08
US federal due date 2022-06-22
Ubuntu priority
medium

CVE-2017-5070 explained

CVE-2017-5070 is a type confusion flaw in the V8 JavaScript engine used by Google Chrome before 59.0.3071.86 on desktop and 59.0.3071.92 on Android. A crafted HTML page can let a remote attacker run arbitrary code inside the browser sandbox. CISA lists it as a known exploited vulnerability.

Impact

A remote attacker who gets a user to open a crafted HTML page can execute arbitrary code inside the sandbox. No privileges are needed and attack complexity is low, but user interaction is required. Successful exploitation can fully compromise confidentiality, integrity and availability within the affected component. CISA added the flaw to its Known Exploited Vulnerabilities catalog on 2022-06-08. Known ransomware use is listed as unknown.

Who is affected

On Ubuntu 14.04 LTS, chromium-browser is fixed in 59.0.3071.109-0ubuntu0.14.04.1186. On Ubuntu 16.04 LTS, chromium-browser is fixed in 59.0.3071.109-0ubuntu0.16.04.1289, but libv8-3.14 and oxide-qt have no fixed version published. Both of these releases are end of life. On Ubuntu 18.04 LTS, libv8-3.14 has no fixed version published. Standard support for 18.04 has ended, and fixes there come only through Ubuntu Pro (ESM).

Written with AI from the data on this page and checked against it automatically.

Official description

Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, 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 Chrome prior to 59.0.3071.86 for Linux, Windows and Mac, and 59.0.3071.92 for Android
    Affected
    • Google Chrome prior to 59.0.3071.86 for Linux, Windows and Mac, and 59.0.3071.92 for Android
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

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.

What to do

  1. On Ubuntu 14.04 LTS and 16.04 LTS, update chromium-browser to the fixed version listed for your release.
  2. Restart all running browser instances so the patched code is loaded.
  3. Plan an upgrade from end-of-life Ubuntu 14.04 LTS and 16.04 LTS to a supported release.
  4. On Ubuntu 18.04 LTS, check whether libv8-3.14 is installed and remove it if nothing depends on it.
  5. Move Ubuntu 18.04 LTS systems to a supported release, or attach Ubuntu Pro to receive any ESM fixes.

libv8-3.14 and oxide-qt on Ubuntu 16.04 LTS, and libv8-3.14 on Ubuntu 18.04 LTS, have no fixed version. Ubuntu 16.04 LTS is end of life and should be upgraded. Do not wait for a fix there. On 18.04, remove these packages if they are unused. Avoid processing untrusted web content with applications that rely on them, and plan an upgrade to a supported release.

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 (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=="chromium-browser"'

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" ;; esac

3. 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.

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/06/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-843 Access of Resource Using Incompatible Type ('Type Confusion')

Questions about CVE-2017-5070

Is CVE-2017-5070 being exploited?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 2022-06-08. The required action is to apply updates per vendor instructions. Whether it has been used in ransomware campaigns is listed as unknown.
Do I need to reboot after updating chromium-browser?
A full reboot is not needed for this browser update. Close and restart every running browser instance, because open sessions keep using the old, vulnerable code until they are restarted.
Why is there no fix for libv8-3.14 or oxide-qt?
No fixed version has been published for these packages on the listed releases. Ubuntu 16.04 LTS is end of life, and standard support for 18.04 LTS has ended. Remove the packages where possible and upgrade to a supported release.

Written with AI from the data on this page and checked against it automatically.

References

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.