xmllint up to 2.11.7/2.12.6 Error Message xmllint.c xmlHTMLPrintFileContext buffer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in xmllint up to 2.11.7/2.12.6. The impacted element is the function xmlHTMLPrintFileContext of the file xmllint.c of the component Error Message Handler. Performing a manipulation results in buffer overflow.
This vulnerability is known as CVE-2024-34459. No exploit is available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in xmllint up to 2.11.7/2.12.6. It has been classified as critical. This affects the function xmlHTMLPrintFileContext of the file xmllint.c of the component Error Message Handler. The manipulation with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7. Formatting error messages with xmllint --htmlout can result in a buffer over-read in xmlHTMLPrintFileContext in xmllint.c.
The advisory is shared at gitlab.gnome.org. This vulnerability is uniquely identified as CVE-2024-34459 since 05/04/2024. The exploitability is told to be easy. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 207713 (Nessus Network Monitor < 6.5.0 Multiple Vulnerabilities (TNS-2024-17)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 2.11.8 or 2.12.7 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (207713) and CERT Bund (WID-SEC-2026-1687). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- IBM License Metric Tool
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA 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: 🔍
Exploiting
Class: Buffer overflowCWE: CWE-120 / CWE-119
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 |
Nessus ID: 207713
Nessus Name: Nessus Network Monitor < 6.5.0 Multiple Vulnerabilities (TNS-2024-17)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: xmllint 2.11.8/2.12.7
Timeline
05/04/2024 🔍05/13/2024 🔍
05/13/2024 🔍
05/28/2026 🔍
Sources
Advisory: gitlab.gnome.orgStatus: Confirmed
CVE: CVE-2024-34459 (🔍)
GCVE (CVE): GCVE-0-2024-34459
GCVE (VulDB): GCVE-100-263985
CERT Bund: WID-SEC-2026-1687 - IBM License Metric Tool: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff
Entry
Created: 05/13/2024 16:25Updated: 05/28/2026 01:57
Changes: 05/13/2024 16:25 (55), 08/22/2024 21:19 (13), 09/30/2024 12:25 (2), 05/28/2026 01:57 (7)
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.