CVE-2018-16068: Input Validation

Published Sep 5, 2018
·
Updated

An out of bounds write flaw was found in the Mojo component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=877182

External References:

https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html

Other sources

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.

MITRE

Affected Software

6 affected componentsFixes available
redhat/chromium-browser<69.0.3497.81
69.0.3497.81
Google Chrome<69.0.3497.81
Debian Debian Linux=9.0
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Workstation=6.0

Remediation

Event History

Jan 9, 2019
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2018-16068?

CVE-2018-16068 has a medium severity rating as it allows a potential sandbox escape in Google Chrome.

2

How do I fix CVE-2018-16068?

To mitigate CVE-2018-16068, upgrade to Google Chrome or Chromium version 69.0.3497.81 or later.

3

Which versions of Chrome are affected by CVE-2018-16068?

CVE-2018-16068 affects Google Chrome versions prior to 69.0.3497.81.

4

What kind of attack does CVE-2018-16068 enable?

CVE-2018-16068 could potentially allow remote attackers to perform a sandbox escape via a crafted HTML page.

5

Is CVE-2018-16068 applicable to any specific operating systems?

CVE-2018-16068 is applicable to multiple operating systems where affected versions of Google Chrome or Chromium are installed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203