CVE-2019-18197: Use After Free
A vulnerabiliy was found in xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable isn't reset under certain circumstances. If the relevant memory area happened to be freed and reused in a certain way, a bounds check could fail and memory outside a buffer could be written to, or uninitialized data could be disclosed.
Reference: https://security.netapp.com/advisory/ntap-20191031-0004/ https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15746 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15768 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15914 https://gitlab.gnome.org/GNOME/libxslt/commit/2232473733b7313d67de8836ea3b29eec6e8e285
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the vulnerability ID of this issue?
The vulnerability ID is CVE-2019-18197.
What is the severity level of CVE-2019-18197?
The severity level of CVE-2019-18197 is high.
Which software is affected by CVE-2019-18197?
The affected software is libxslt version 1.1.33.
How can I fix CVE-2019-18197?
To fix CVE-2019-18197, you should update to libxslt version 1.1.34 or higher.
Are there any references for CVE-2019-18197?
Yes, you can find references for CVE-2019-18197 at the following links: [Reference 1](http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00010.html), [Reference 2](http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00015.html), [Reference 3](http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00025.html).