VDB

CVE-2018-18342

CVE-2018-18342 PUBLISHED

Reported by chrome · Published December 11, 2018

Execution of user supplied Javascript during object deserialization can update object length 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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
chromiumArch Linux71.0.3578.80-1
chromegoogle71.0.3578.80
chromium-browserUbuntu:18.04:LTS71.0.3578.80-0ubuntu0.18.04.1
chromium-browserUbuntu:16.04:LTS71.0.3578.80-0ubuntu0.16.04.1

Affected products

VendorProductVersions
GoogleChromeunspecified
GoogleChrome*
archchromium0

Timeline

  • Dec 5, 2018 CVE Published
  • Sep 25, 2019 PoC Published (7 in total, the first dated here)
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Apr 17, 2026 Distribution Patch (2 in total, the first dated here)
  • Apr 17, 2026 Security Advisory (5 in total, the first dated here)
  • Jun 17, 2026 CVE Updated
  • Sep 22, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2018-18342
vulnetix vdb fixes CVE-2018-18342

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2018-18342/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›