Eclipse Vert.x 3.5.0/3.5.1/3.5.2/3.5.3 OpenAPI XML Parser xml external entity reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Eclipse Vert.x 3.5.0/3.5.1/3.5.2/3.5.3. Affected by this vulnerability is an unknown functionality of the component OpenAPI XML Parser. Executing a manipulation can lead to xml external entity reference. The identification of this vulnerability is CVE-2018-12544. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability was found in Eclipse Vert.x 3.5.0/3.5.1/3.5.2/3.5.3. It has been declared as critical. This vulnerability affects an unknown functionality of the component OpenAPI XML Parser. The manipulation with an unknown input leads to a xml external entity reference vulnerability. The CWE definition for the vulnerability is CWE-611. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
In version from 3.5.Beta1 to 3.5.3 of Eclipse Vert.x, the OpenAPI XML type validator creates XML parsers without taking appropriate defense against XML attacks. This mechanism is exclusively when the developer uses the Eclipse Vert.x OpenAPI XML type validator to validate a provided schema.
The bug was discovered 10/10/2018. The weakness was shared 10/10/2018 (Website). The advisory is shared for download at bugs.eclipse.org. This vulnerability was named CVE-2018-12544 since 06/18/2018. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-125223 and VDB-125222 are related to this item. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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 external entity referenceCWE: CWE-611 / CWE-610
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: 🔍
Timeline
06/18/2018 🔍10/10/2018 🔍
10/10/2018 🔍
10/10/2018 🔍
10/11/2018 🔍
05/25/2023 🔍
Sources
Advisory: RHSA-2018:2946Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-12544 (🔍)
GCVE (CVE): GCVE-0-2018-12544
GCVE (VulDB): GCVE-100-125224
See also: 🔍
Entry
Created: 10/11/2018 11:40Updated: 05/25/2023 08:27
Changes: 10/11/2018 11:40 (56), 05/26/2020 08:19 (2), 05/25/2023 08:27 (3)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.