ChromeWeb browser · Google

CVE-2018-16067

MEDIUM · 6.5 CVSS v3.0 Published 2019-01-09

Fix available

A fix is available. Upgrade to 69.0.3497.81 or later.

See remediation →

72/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

A use after free in WebAudio in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Technical summary

dbcve analysis · high confidence

Use-after-free vulnerability in Google Chrome's WebAudio component allows a remote attacker to potentially exploit heap corruption via a specially crafted HTML page. The vulnerability exists in versions prior to 69.0.3497.81 and can be triggered when a user visits a malicious webpage.

MitigationUpdate Google Chrome to version 69.0.3497.81 or later to remediate this vulnerability. Organizations should deploy browser updates through their patch management infrastructure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 69.0.3497.81

Debian LinuxOperating system

Affected:= 9.0

Enterprise Linux DesktopOperating system

Affected:= 6.0

Enterprise Linux ServerOperating system

Affected:= 6.0

Enterprise Linux WorkstationOperating system

Affected:= 6.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify Google Chrome is installed

Check for Chrome executable: On Windows, look in Program Files/Google/Chrome/Application/chrome.exe. On Linux, run 'which google-chrome' or 'which chromium-browser'. On macOS, check /Applications/Google Chrome.app

Affected if Chrome is not installed on the system - the user is not affected via this browser, though other browsers could still pose risks
Determine installed Chrome version

Open Chrome, click menu > Help > About Google Chrome, or navigate to chrome://settings/help. Alternatively, run 'google-chrome --version' (Linux) or 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' (Windows)

Affected if The displayed version is lower than 69.0.3497.81 - the user is likely affected by this vulnerability
Check Chrome version on Debian Linux

Run 'dpkg -l | grep chrome' or 'apt-cache policy google-chrome-stable' to see the installed Chrome package version on Debian systems

Affected if The installed version on Debian 9.0 is below 69.0.3497.81 - the system is vulnerable if Chrome is installed
Check Chrome version on RHEL/CentOS

Run 'rpm -qa | grep -i chrome' to list installed Chrome RPM packages on Red Hat Enterprise Linux systems

Affected if Chrome version on RHEL 6.0 Desktop/Server/Workstation is below 69.0.3497.81 - the vulnerability is present
Confirm WebAudio is enabled

Navigate to chrome://settings/content in Chrome. Under 'Additional content settings', verify WebAudio API is not explicitly blocked. Alternatively, this is a default-enabled feature and the vulnerability triggers through normal webpage usage

Affected if WebAudio is enabled (default state) and Chrome version is below 69.0.3497.81 - the exploitation condition is met when visiting malicious pages

A user is affected if Google Chrome (or Chromium) version 69.0.3497.81 or higher is NOT installed, and the WebAudio feature remains in its default enabled state, allowing the specially crafted HTML page to trigger the use-after-free.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to 69.0.3497.81 or later

Fixed in 69.0.3497.81

Interim mitigation

Update Google Chrome to version 69.0.3497.81 or later to remediate this vulnerability. Organizations should deploy browser updates through their patch management infrastructure.

Fix this in Chrome Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2018-16067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-16067 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2018-16067?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to 69.0.3497.81 or later

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 1.4%

Affects: Chrome

Remediation

Need this fixed?

Fix this in Chrome 9 hrs · Low

Typical engagement from $1,600

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2018-16067 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References