ChromeWeb browser · Google

CVE-2018-16068

CRITICAL · 9.6 CVSS v3.0 Published 2019-01-09

Fix available

A fix is available. Upgrade to 69.0.3497.81 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges

Official description

NVD · unedited

Missing validation in Mojo in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page.

Technical summary

dbcve analysis · high confidence

Missing validation in Mojo (Chromium's platform abstraction layer) in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. This is a critical validation flaw that enables bypassing Chrome's multi-process sandbox security mechanism.

MitigationUpdate Google Chrome to version 69.0.3497.81 or later to patch the validation vulnerability in Mojo.

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: Changed
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

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

Check installed Google Chrome version

Open Chrome, click the menu icon (three dots), select Help, then About Google Chrome. Alternatively, navigate to chrome://settings/help or run 'google-chrome --version' in terminal

Affected if Version number displayed is lower than 69.0.3497.81
Verify Debian Linux version

Check the OS version by running 'cat /etc/debian_version' or 'lsb_release -a' in terminal

Affected if The system reports Debian Linux version 9.0
Verify Red Hat Enterprise Linux version

Check the OS version by running 'cat /etc/redhat-release' or 'cat /etc/os-release' in terminal

Affected if The system reports RHEL Desktop 6.0, RHEL Server 6.0, or RHEL Workstation 6.0
Confirm Chrome is the affected component

Ensure Chrome browser is installed and actively used on the system. On RHEL/Debian systems, check if the bundled Chromium/Chrome package is present via 'dpkg -l | grep -i chrome' or 'rpm -qa | grep -i chrome'

Affected if Chrome is installed on a Debian 9.0 or RHEL 6.0 system, or Chrome version is below 69.0.3497.81 on any platform

You are affected if Google Chrome version is lower than 69.0.3497.81, or if running Chrome on Debian 9.0 or RHEL 6.0 (Desktop/Server/Workstation), as these OS versions shipped with vulnerable Chrome versions.

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

Remediation

dbcve · scoped

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 patch the validation vulnerability in Mojo.

Recommended fix High confidence

Chrome 69.0.3497.81 or later (stable release)

Open Google Chrome
Navigate to Settings > Help > About Google Chrome
Chrome will automatically check for and download the latest stable update (version 69.0.3497.81 or later)
Restart Chrome to apply the update
Verify the update was applied by returning to Help > About Google Chrome and confirming the version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing1.0 h
Review / QA1.0 h

5.0 hours of engineering $910

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2018-16068 — 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-16068 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2018-16068?

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 9.6 Critical

Exploit likelihood EPSS, next 30 days 1.9%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 5 hrs · Low

Typical engagement from $910

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2018-16068 and return a fixed quote and timeline.

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