Vulnerability Details : CVE-2019-18197

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.
Published 2019-10-18 21:15:11
Updated 2020-08-24 17:37:01
Source MITRE
View at NVD,   CVE.org

Products affected by CVE-2019-18197

Exploit prediction scoring system (EPSS) score for CVE-2019-18197

EPSS FAQ
1.48%
Probability of exploitation activity in the next 30 days EPSS Score History
~ 79 %
Percentile, the proportion of vulnerabilities that are scored at or less

CVSS scores for CVE-2019-18197

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
5.1
 MEDIUM AV:N/AC:H/Au:N/C:P/I:P/A:P
4.9
6.4
 NIST
7.5
 HIGH CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
1.6
5.9
 NIST

CWE ids for CVE-2019-18197

  • The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
    Assigned by: nvd@nist.gov (Primary)
  • The product uses or accesses a resource that has not been initialized.
    Assigned by: nvd@nist.gov (Primary)

References for CVE-2019-18197

Jump to
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!
Accept Close