CVE-2018-6170: Type confusion in PDFium
A bad cast in PDFium in Google Chrome prior to 68.0.3440.75 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file.
Other sources
A type confusion flaw was found in the PDFium component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=862059
External References:
https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html
— Red Hat
Credit
Affected Software
Remediation
Patch Available
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2018-6153
- CVE-2018-6154
- CVE-2018-6155
- CVE-2018-6156
- CVE-2018-6157
- CVE-2018-6158
- CVE-2018-6159
- CVE-2018-6160
- CVE-2018-6161
- CVE-2018-6162
- CVE-2018-6163
- CVE-2018-6164
- CVE-2018-6165
- CVE-2018-6166
- CVE-2018-6167
- CVE-2018-6168
- CVE-2018-6169
- CVE-2018-6171
- CVE-2018-6172
- CVE-2018-6173
- CVE-2018-6174
- CVE-2018-6175
- CVE-2018-6176
- CVE-2018-6177
- CVE-2018-6178
- CVE-2018-6179
- CVE-2018-6044
- CVE-2018-4117
- CVE-2018-17460
- CVE-2018-17461
- CVE-2018-6150
- CVE-2018-6151
- CVE-2018-6152
Frequently Asked Questions
What is CVE-2018-6170?
CVE-2018-6170 is a vulnerability in PDFium in Google Chrome prior to 68.0.3440.75.
How does CVE-2018-6170 affect Google Chrome?
CVE-2018-6170 can potentially allow a remote attacker to exploit heap corruption via a crafted PDF file.
What is the severity of CVE-2018-6170?
CVE-2018-6170 has a severity score of 8.8 (high).
How can I fix CVE-2018-6170 in Google Chrome?
To fix CVE-2018-6170, you need to update Google Chrome to version 68.0.3440.75 or later.
Are there any additional references for CVE-2018-6170?
Yes, you can find more information about CVE-2018-6170 at the following references: [Reference 1](https://code.google.com/p/chromium/issues/detail?id=862059), [Reference 2](https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html), [Reference 3](https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1608211).