Out-of-bounds Write Affecting chromium-browser package, versions <62.0.3202.75-1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN9-CHROMIUMBROWSER-408503
- published7 Feb 2018
- disclosed7 Feb 2018
Introduced: 7 Feb 2018
CVE-2017-5130 (opens in a new tab)How to fix?
Upgrade Debian:9 chromium-browser to version 62.0.3202.75-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream chromium-browser package and not the chromium-browser package as distributed by Debian.
See How to fix? for Debian:9 relevant fixed versions and status.
An integer overflow in xmlmemory.c in libxml2 before 2.9.5, as used in Google Chrome prior to 62.0.3202.62 and other products, allowed a remote attacker to potentially exploit heap corruption via a crafted XML file.
References
- https://security-tracker.debian.org/tracker/CVE-2017-5130
- https://crbug.com/722079
- https://lists.debian.org/debian-lts-announce/2017/11/msg00034.html
- https://security.gentoo.org/glsa/201710-24
- http://bugzilla.gnome.org/show_bug.cgi?id=783026
- https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html
- https://git.gnome.org/browse/libxml2/commit/?id=897dffbae322b46b83f99a607d527058a72c51ed
- https://www.oracle.com/security-alerts/cpuapr2020.html
- https://security.netapp.com/advisory/ntap-20190719-0001/
- https://access.redhat.com/errata/RHSA-2017:2997
- http://www.securityfocus.com/bid/101482
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-5130
- https://lists.debian.org/debian-lts-announce/2022/04/msg00004.html