libxslt 1.1.33 numbers.c xsltNumberFormatDecimal type confusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in libxslt 1.1.33. This impacts the function xsltNumberFormatDecimal of the file numbers.c. This manipulation causes input validation.
This vulnerability appears as CVE-2019-13118. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in libxslt 1.1.33. It has been declared as critical. Affected by this vulnerability is the function xsltNumberFormatDecimal of the file numbers.c. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-843. The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The weakness was presented 07/01/2019 (Website). The advisory is shared at seclists.org. This vulnerability is known as CVE-2019-13118 since 06/30/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-137112, VDB-138544, VDB-138575 and VDB-138632 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
ADP CISA Base Score: 5.3
ADP CISA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Type confusionCWE: CWE-843
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: gitlab.gnome.org
Timeline
06/30/2019 🔍07/01/2019 🔍
07/01/2019 🔍
05/29/2026 🔍
Sources
Advisory: 6ce8de69330783977dd14f6569419489875fb71bStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2019-13118 (🔍)
GCVE (CVE): GCVE-0-2019-13118
GCVE (VulDB): GCVE-100-137113
See also: 🔍
Entry
Created: 07/01/2019 09:19Updated: 05/29/2026 06:10
Changes: 07/01/2019 09:19 (54), 06/29/2020 12:38 (2), 10/09/2023 17:09 (4), 10/09/2023 17:16 (1), 05/29/2026 06:10 (35)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.