CVE-2018-6144: High severity Google Chrome vulnerability

Q: What must an attacker do to exploit this issue?

An attacker must get a user to open or otherwise process a crafted PDF file in an affected Chromium-based browser. The attack can be delivered remotely and requires no prior privileges, but user interaction is required.

Q: Which browser versions are affected?

Google Chrome versions before 67.0.3396.62 are affected. The listed Chromium browser packages for Debian and Red Hat Enterprise Linux systems may also be affected; verify the vendor-provided package update status for the installed system.

Q: What is the likely impact if exploitation succeeds?

Successful exploitation can cause an out-of-bounds memory write in PDFium. The supplied severity vector indicates potential high impact to confidentiality, integrity, and availability.

Q: What can be done if the browser cannot be updated immediately?

Avoid opening PDF files from untrusted or unexpected sources in the affected browser until an update is installed. Because exploitation requires a crafted PDF and user interaction, reducing exposure to untrusted PDFs is a relevant temporary mitigation.

Published May 30, 2018

Updated

An out of bounds memory access flaw was found in the PDFium component of the Chromium browser.

Upstream bug(s):

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

External References:

https://chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop58.html

Other sources

Off-by-one error in PDFium in Google Chrome prior to 67.0.3396.62 allowed a remote attacker to perform an out of bounds memory write via a crafted PDF file.

Affected Software

7 affected componentsFixes available

debian/chromium-browser

redhat/chromium-browser<67.0.3396.62

67.0.3396.62

Google Chrome<67.0.3396.62

Debian Debian Linux=9.0

redhat Enterprise Linux Desktop=6.0

redhat Enterprise Linux Server=6.0

redhat Enterprise Linux Workstation=6.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade redhat/chromium-browser to a version that resolves this vulnerability.
Fixed in 67.0.3396.62
Upgrade
Upgrade Google Chrome/Chromium to a version that resolves this vulnerability.
Fixed in 67.0.3396.62

Event History

May 30, 2018

Data Sourced

via Red Hat·07:58 AM

DescriptionSeverityAffected Software

Jan 9, 2019

CVE Published

via MITRE·07:00 PM

Data Sourced

via MITRE·07:00 PM

DescriptionWeakness

Frequently Asked Questions

What must an attacker do to exploit this issue?

An attacker must get a user to open or otherwise process a crafted PDF file in an affected Chromium-based browser. The attack can be delivered remotely and requires no prior privileges, but user interaction is required.

Which browser versions are affected?

Google Chrome versions before 67.0.3396.62 are affected. The listed Chromium browser packages for Debian and Red Hat Enterprise Linux systems may also be affected; verify the vendor-provided package update status for the installed system.

What is the likely impact if exploitation succeeds?

Successful exploitation can cause an out-of-bounds memory write in PDFium. The supplied severity vector indicates potential high impact to confidentiality, integrity, and availability.

What can be done if the browser cannot be updated immediately?

Avoid opening PDF files from untrusted or unexpected sources in the affected browser until an update is installed. Because exploitation requires a crafted PDF and user interaction, reducing exposure to untrusted PDFs is a relevant temporary mitigation.

CVE-2018-6144: High severity Google Chrome vulnerability

Other sources

Affected Software

Remediation

Event History

Frequently Asked Questions

What must an attacker do to exploit this issue?

Which browser versions are affected?

What is the likely impact if exploitation succeeds?

What can be done if the browser cannot be updated immediately?

Company

Resources

Contact

Frequently Asked Questions

What must an attacker do to exploit this issue?

Which browser versions are affected?

What is the likely impact if exploitation succeeds?

What can be done if the browser cannot be updated immediately?