CVE-2017-15408: Buffer Overflow
A heap buffer overflow flaw was found in the PDFium component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=762374
External References:
https://chromereleases.googleblog.com/2017/12/stable-channel-update-for-desktop.html
Other sources
Heap buffer overflow in Omnibox in Google Chrome prior to 63.0.3239.84 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file that is mishandled by PDFium.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/chromium-browserto a version that resolves this vulnerability.Fixed in 63.0.3239.84 - Upgrade
Upgrade
Google Chrometo a version that resolves this vulnerability.Fixed in 63.0.3239.84
Event History
Frequently Asked Questions
What is the severity of CVE-2017-15408?
CVE-2017-15408 is classified as a medium severity vulnerability due to its potential to cause a heap buffer overflow.
How do I fix CVE-2017-15408?
To fix CVE-2017-15408, update the Chromium browser to version 63.0.3239.84 or later.
Which software is affected by CVE-2017-15408?
CVE-2017-15408 affects the Chromium browser and Google Chrome versions prior to 63.0.3239.84.
What type of vulnerability is CVE-2017-15408?
CVE-2017-15408 is a heap buffer overflow vulnerability found in the PDFium component of the Chromium browser.
Is CVE-2017-15408 exploitable remotely?
Yes, CVE-2017-15408 can be potentially exploited remotely through maliciously crafted PDF files.