| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in libxml. This affects an unknown function of the component xmlreader. The manipulation results in resource management. This vulnerability is known as CVE-2015-1819. No exploit is available.
Details
A vulnerability, which was classified as problematic, was found in libxml (unknown version). Affected is an unknown code block of the component xmlreader. The manipulation with an unknown input leads to a resource management vulnerability. CWE is classifying the issue as CWE-399. This is going to have an impact on availability. CVE summarizes:
The xmlreader in libxml allows remote attackers to cause a denial of service (memory consumption) via crafted XML data, related to an XML Entity Expansion (XEE) attack.
The weakness was published 08/14/2015 by Florian Weimer (Website). The advisory is available at git.gnome.org. This vulnerability is traded as CVE-2015-1819 since 02/17/2015. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.
The vulnerability scanner Nessus provides a plugin with the ID 85019 (CentOS 6 : libxml2 (CESA-2015:1419)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 351588 (Amazon Linux Security Advisory for libxml2: ALAS2-2019-1220).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Tenable (85019) and SecurityFocus (BID 75570†). Similar entries are available at VDB-79257, VDB-79258, VDB-79334 and VDB-79335. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Resource managementCWE: CWE-399 / CWE-404
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: 85019
Nessus Name: CentOS 6 : libxml2 (CESA-2015:1419)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
OpenVAS ID: 14611
OpenVAS Name: Amazon Linux Local Check: alas-2015-628
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: git.gnome.org
Timeline
02/17/2015 🔍07/07/2015 🔍
08/14/2015 🔍
08/14/2015 🔍
08/15/2015 🔍
06/12/2022 🔍
Sources
Advisory: RHSA-2015:1419Researcher: Florian Weimer
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2015-1819 (🔍)
GCVE (CVE): GCVE-0-2015-1819
GCVE (VulDB): GCVE-100-77250
OVAL: 🔍
SecurityFocus: 75570 - Libxml2 CVE-2015-1819 Denial of Service Vulnerability
SecurityTracker: 1034243
See also: 🔍
Entry
Created: 08/15/2015 21:15Updated: 06/12/2022 10:54
Changes: 08/15/2015 21:15 (45), 10/09/2017 09:50 (17), 06/12/2022 10:41 (5), 06/12/2022 10:47 (1), 06/12/2022 10:54 (2)
Complete: 🔍
Cache ID: 216:DB8:103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.