Red Hat XML Language Support up to 0.9.0 LSPXMLParserConfiguration.java XML Document xml injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Red Hat XML Language Support up to 0.9.0. Affected by this issue is some unknown functionality of the file extensions/contentmodel/participants/diagnostics/LSPXMLParserConfiguration.java. The manipulation as part of XML Document leads to xml injection. This vulnerability is documented as CVE-2019-18213. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Red Hat XML Language Support up to 0.9.0. This issue affects some unknown processing of the file extensions/contentmodel/participants/diagnostics/LSPXMLParserConfiguration.java. The manipulation as part of a XML Document leads to a xml injection vulnerability. Using CWE to declare the problem leads to CWE-91. The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
XML Language Server (aka lsp4xml) before 0.9.1, as used in Red Hat XML Language Support (aka vscode-xml) before 0.9.1 for Visual Studio and other products, allows XXE via a crafted XML document, with resultant SSRF (as well as SMB connection initiation that can lead to NetNTLM challenge/response capture for password cracking). This occurs in extensions/contentmodel/participants/diagnostics/LSPXMLParserConfiguration.java.
The weakness was released 10/23/2019 (GitHub Repository). The advisory is shared at github.com. The identification of this vulnerability is CVE-2019-18213 since 10/19/2019. The attack may be initiated remotely. Required for exploitation is a simple authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
Upgrading to version 0.9.1 eliminates this vulnerability.
Entry connected to this vulnerability is available at VDB-144100. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.redhat.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.2
VulDB Base Score: 6.3
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD 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: Xml injectionCWE: CWE-91 / CWE-74 / CWE-707
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: XML Language Support 0.9.1
Patch: github.com
Timeline
10/19/2019 🔍10/23/2019 🔍
10/24/2019 🔍
01/27/2024 🔍
Sources
Vendor: redhat.comAdvisory: github.com
Status: Not defined
CVE: CVE-2019-18213 (🔍)
GCVE (CVE): GCVE-0-2019-18213
GCVE (VulDB): GCVE-100-144101
See also: 🔍
Entry
Created: 10/24/2019 12:41Updated: 01/27/2024 08:12
Changes: 10/24/2019 12:41 (41), 10/24/2019 12:46 (17), 01/27/2024 08:12 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.