XMLSoft libxslt 1.1.33
Approved changes feed: RSS · Atom
cpe:2.3:a:xmlsoft:libxslt:1.1.33:*:*:*:*:*:*:*
part: a version: 1.1.33 update: *
| Vendor | Xmlsoft (be3c3366-cde4-54a5-8785-eb1f04df6881) |
|---|---|
| Product | Libxslt (9dcdf0d8-a99c-518f-887f-5cc8a5a57af8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/coapp-packages/libxslt |
purl2cpe | 2026-06-01 10:12:19.484454 |
pkg:github/gnome/libxslt |
purl2cpe | 2026-06-01 10:12:19.484456 |
pkg:gitlab/redhat/libxslt |
purl2cpe | 2026-06-01 10:12:19.484457 |
pkg:nuget/libxslt |
purl2cpe | 2026-06-01 10:12:19.484458 |
pkg:rpm/fedora/libxslt |
purl2cpe | 2026-06-01 10:12:19.484460 |
pkg:rpm/opensuse/libxslt |
purl2cpe | 2026-06-01 10:12:19.484461 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-18197 |
vulnerable | 2026-06-08 05:13:11.002904 |
Details available
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-18T20:07:17.000Z
Updated: 2026-05-28T18:27:59.540Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-13118 |
vulnerable | 2026-06-08 05:12:40.932542 |
Details available
In numbers.c in libxslt 1.1.33, a type holding grouping characters of an xsl:number instruction was too narrow and an invalid character/length combination could be passed to xsltNumberFormatDecimal, leading to a read of uninitialized stack data.
Published: 2019-07-01T01:27:39.000Z
Updated: 2026-05-28T18:36:48.291Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-13117 |
vulnerable | 2026-06-08 05:12:40.928972 |
Details available
In numbers.c in libxslt 1.1.33, an xsl:number with certain format strings could lead to a uninitialized read in xsltNumberFormatInsertNumbers. This could allow an attacker to discern whether a byte on the stack contains the characters A, a, I, i, or 0, or any other character.
Published: 2019-07-01T01:27:02.000Z
Updated: 2026-05-28T18:31:25.861Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.