Skip to content
Server Security Center
KEVhigh8.8

CVE-2018-17463: Google Chromium V8 Remote Code Execution

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

CVE-2018-17463 explained

CVE-2018-17463 is an incorrect side effect annotation in the V8 JavaScript engine used by Google Chrome before 70.0.3538.64. A remote attacker can run arbitrary code inside the browser sandbox through a crafted HTML page. CISA lists it as a known exploited vulnerability, so affected systems should be patched promptly.

Impact

An attacker who gets a user to open a crafted HTML page can execute arbitrary code inside the sandbox. The attack works over the network, needs no privileges and has low complexity, but requires user interaction. Confidentiality, integrity and availability impacts are all rated high. The scope is unchanged, so the code runs within the sandbox of the affected process.

Who is affected

On Ubuntu 16.04 LTS, which is end of life, chromium-browser is fixed in 70.0.3538.67-0ubuntu0.16.04.1. The oxide-qt package on the same release has no fixed version published. On Ubuntu 18.04 LTS, chromium-browser is fixed in 70.0.3538.67-0ubuntu0.18.04.1 in the standard archive. Standard support for 18.04 has ended, and further fixes there come only with Ubuntu Pro (ESM).

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

Official description

Incorrect side effect annotation in V8 in Google Chrome prior to 70.0.3538.64 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
    Affected
    • < 70.0.3538.64
    Fixed in
    • 70.0.3538.64

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. Update chromium-browser to 70.0.3538.67-0ubuntu0.16.04.1 or later on Ubuntu 16.04 LTS.
  2. Update chromium-browser to 70.0.3538.67-0ubuntu0.18.04.1 or later on Ubuntu 18.04 LTS.
  3. Restart all running browser instances so they load the patched code.
  4. Find systems that have oxide-qt installed on Ubuntu 16.04 LTS, and remove it where it is not needed.
  5. Plan an upgrade of Ubuntu 16.04 LTS systems to a supported release.
  6. Consider Ubuntu Pro (ESM) for Ubuntu 18.04 LTS systems so they keep receiving security fixes.

oxide-qt on Ubuntu 16.04 LTS has no fixed version published, and the release is end of life. Upgrade these systems to a supported release. Until then, remove oxide-qt if nothing depends on it. Otherwise, keep applications that use it away from untrusted web content and limit their 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 chromium-browser with the source package from the table above (this CVE affects 2 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

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.

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

Questions about CVE-2018-17463

Is this vulnerability being exploited?
Yes. CISA added CVE-2018-17463 to its Known Exploited Vulnerabilities catalog on 2022-06-08. 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 victim must open a crafted HTML page, for example by visiting a malicious website.
Do I need to restart anything after updating?
Yes. A browser that is already running keeps using the old code until it is restarted. Close and reopen all Chromium instances after you install the update.

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-21. Always confirm with the vendor's or distribution's advisory before patching.