Apache Xerces Jelly Parser XML File xml external entity reference

entryeditHistoryDiffjsonxmlCTI
CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.5$5k-$25k0.00

A vulnerability was found in Apache Xerces (affected version unknown). 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 vulnerability. The CWE definition for the vulnerability is CWE-611. 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 by Luca Carettoni (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 databases at SecurityFocus (BID 101052) and SecurityTracker (ID 1039444).

Productinfoedit

Vendor

Name

CPE 2.3infoedit

CPE 2.2infoedit

CVSSv3infoedit

VulDB Meta Base Score: 8.5
VulDB 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: 🔍

CVSSv2infoedit

AVACAuCIA
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfoedit

Class: XML External Entity
CWE: CWE-611
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfoedit

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍

Countermeasuresinfoedit

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfoedit

08/07/2017 🔍
09/25/2017 +49 days 🔍
09/27/2017 +2 days 🔍
09/27/2017 +0 days 🔍
09/28/2017 +1 days 🔍
09/28/2017 +0 days 🔍
01/14/2021 +1204 days 🔍

Sourcesinfoedit

Vendor: https://www.apache.org/

Advisory: lists.apache.org
Researcher: Luca Carettoni
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-12621 (🔍)
SecurityFocus: 101052 - Apache Commons Jelly CVE-2017-12621 Security Bypass Vulnerability
SecurityTracker: 1039444

Entryinfoedit

Created: 09/28/2017 11:10 AM
Updated: 01/14/2021 03:32 PM
Changes: (1) advisory_person_name
Complete: 🔍

Comments

No comments yet. Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!