libxslt: use after free in xsltCopyText in transform.c could lead to information disclosure
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
| AND |
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 6 Supplementary | |||
| chromium-browser-0:80.0.3987.87-1.el6_10 | cpe:/a:redhat:rhel_extras:6 | RHSA-2020:0514 | 2020-02-17T00:00:00Z |
| Red Hat Enterprise Linux 7 | |||
| libxslt-0:1.1.28-6.el7 | cpe:/o:redhat:enterprise_linux:7 | RHSA-2020:4005 | 2020-09-29T00:00:00Z |
| Red Hat Enterprise Linux 8 | |||
| libxslt-0:1.1.32-5.el8 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2020:4464 | 2020-11-04T00:00:00Z |
| libxslt-0:1.1.32-5.el8 | cpe:/o:redhat:enterprise_linux:8 | RHSA-2020:4464 | 2020-11-04T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-1973-1 | libxslt security update |
EUVD |
EUVD-2022-1901 | 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. |
Github GHSA |
GHSA-242x-7cm6-4w8j | Nokogiri affected by libxslt Use of Uninitialized Resource/Use After Free vulnerability |
Ubuntu USN |
USN-4164-1 | Libxslt vulnerabilities |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 4.4% (4.446% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|