Vulnerability Description
Off-by-one read/write on the heap in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to corrupt memory and possibly leak information and potentially execute code via a crafted PDF file.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Chrome | < 62.0.3202.62 | |
| Debian | Debian Linux | 8.0 |
Related Weaknesses (CWE)
References
- http://www.securityfocus.com/bid/101482
- https://access.redhat.com/errata/RHSA-2017:2997
- https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.
- https://crbug.com/762106
- https://security.gentoo.org/glsa/201710-24
- https://www.debian.org/security/2017/dsa-4020
- http://www.securityfocus.com/bid/101482
- https://access.redhat.com/errata/RHSA-2017:2997
- https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.
- https://crbug.com/762106
- https://security.gentoo.org/glsa/201710-24
- https://www.debian.org/security/2017/dsa-4020
FAQ
What is CVE-2017-5133?
CVE-2017-5133 is a vulnerability with a CVSS score of 8.8 (HIGH). Off-by-one read/write on the heap in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to corrupt memory and possibly leak information and potentially execute code via a crafted P...
How severe is CVE-2017-5133?
CVE-2017-5133 has been rated HIGH with a CVSS base score of 8.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2017-5133?
Check the references section above for vendor advisories and patch information. Affected products include: Google Chrome, Debian Debian Linux.