Apache Xerces Jelly Parser XML File xml external entity reference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as critical has been found in Apache Xerces. This affects an unknown part of the component Jelly Parser. This manipulation as part of XML File causes xml external entity reference. This vulnerability is tracked as CVE-2017-12621. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Apache Xerces (version now known). It has been declared as critical. Affected by this vulnerability is some unknown processing of the component Jelly Parser. The manipulation as part of a XML File 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. The summary by CVE is:
During Jelly (xml) file parsing with Apache Xerces, if a custom doctype entity is declared with a "SYSTEM" entity with a URL and that entity is used in the body of the Jelly file, during parser instantiation the parser will attempt to connect to said URL. This could lead to XML External Entity (XXE) attacks in Apache Commons Jelly before 1.0.1.
The bug was discovered 09/27/2017. The weakness was disclosed 09/28/2017 (Website). The advisory is shared at lists.apache.org. This vulnerability is known as CVE-2017-12621 since 08/07/2017. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/14/2021).
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 vulnerability database at SecurityFocus (BID 101052†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
Website
- Vendor: https://www.apache.org/
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
08/07/2017 🔍09/25/2017 🔍
09/27/2017 🔍
09/27/2017 🔍
09/28/2017 🔍
09/28/2017 🔍
01/14/2021 🔍
Sources
Vendor: apache.orgAdvisory: lists.apache.org
Researcher: Luca Carettoni
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-12621 (🔍)
GCVE (CVE): GCVE-0-2017-12621
GCVE (VulDB): GCVE-100-107197
SecurityFocus: 101052 - Apache Commons Jelly CVE-2017-12621 Security Bypass Vulnerability
SecurityTracker: 1039444
Entry
Created: 09/28/2017 11:10Updated: 01/14/2021 15:32
Changes: 09/28/2017 11:10 (58), 11/20/2019 09:06 (3), 01/14/2021 15:28 (3), 01/14/2021 15:32 (1)
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.