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
Link | Resource |
---|---|
http://bugzilla.gnome.org/show_bug.cgi?id=783026 | Issue Tracking |
http://www.securityfocus.com/bid/101482 | Third Party Advisory VDB Entry |
https://access.redhat.com/errata/RHSA-2017:2997 | Third Party Advisory |
https://chromereleases.googleblog.com/2017/10/stable-channel-update-for-desktop.html | Vendor Advisory |
https://crbug.com/722079 | Third Party Advisory |
https://git.gnome.org/browse/libxml2/commit/?id=897dffbae322b46b83f99a607d527058a72c51ed | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2017/11/msg00034.html | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2022/04/msg00004.html | |
https://security.gentoo.org/glsa/201710-24 | Third Party Advisory |
https://security.netapp.com/advisory/ntap-20190719-0001/ | |
https://www.oracle.com/security-alerts/cpuapr2020.html |
Configurations
History
No history.
Information
Published : 2018-02-07 23:29
Updated : 2024-02-28 16:25
NVD link : CVE-2017-5130
Mitre link : CVE-2017-5130
CVE.ORG link : CVE-2017-5130
JSON object : View
Products Affected
- chrome
debian
- debian_linux
xmlsoft
- libxml2
CWE
CWE-787
Out-of-bounds Write