CVE-2017-5133

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.

References

Link	Tags
http://www.securityfocus.com/bid/101482	vdb entry
https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html
https://crbug.com/762106
https://www.debian.org/security/2017/dsa-4020	vendor advisory
https://access.redhat.com/errata/RHSA-2017:2997	vendor advisory
https://security.gentoo.org/glsa/201710-24	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-5133?: CVE-2017-5133 has been scored as a high severity vulnerability.
How to fix CVE-2017-5133?: To fix CVE-2017-5133, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-5133 being actively exploited in the wild?: It is possible that CVE-2017-5133 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~3% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-5133?: CVE-2017-5133 affects n/a Google Chrome prior to 62.0.3202.62.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.

Description

Category

CWE-787 – Out-of-bounds Write

References

Frequently Asked Questions