CVE-2019-18197
moderate-risk
Published 2019-10-18
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.
Do I need to act?
~
4.5% chance of exploitation in next 30 days
EPSS score — moderate exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
7
CVSS 7.5/10
High
NETWORK
/ HIGH complexity
Affected Products (8)
References (30)
Issue Tracking
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15746
Issue Tracking
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15768
Issue Tracking
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15914
Third Party Advisory
https://lists.debian.org/debian-lts-announce/2019/10/msg00037.html
Third Party Advisory
https://security.netapp.com/advisory/ntap-20191031-0004/
Third Party Advisory
https://usn.ubuntu.com/4164-1/
and 10 more references
44
/ 100
moderate-risk
Severity
22/34 · High
Exploitability
8/34 · Low
Exposure
14/34 · Moderate