CVE-2017-5009
WebRTC in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, failed to perform proper bounds checking, which allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.42%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
WebRTC in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, failed to perform proper bounds checking, which allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
- CVSS 3.0
- 8.8 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS
- 1.42% probability · 71th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-119
- Affected
- google/chrome
- Source
- chrome-cve-admin@google.com
References
- http://rhn.redhat.com/errata/RHSA-2017-0206.html
- http://www.debian.org/security/2017/dsa-3776
- http://www.securityfocus.com/bid/95792
- http://www.securitytracker.com/id/1037718
- https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html
- https://crbug.com/667504
- https://security.gentoo.org/glsa/201701-66
- http://rhn.redhat.com/errata/RHSA-2017-0206.html
- http://www.debian.org/security/2017/dsa-3776
- http://www.securityfocus.com/bid/95792
- http://www.securitytracker.com/id/1037718
- https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html
- https://crbug.com/667504
- https://security.gentoo.org/glsa/201701-66
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.