Oracle Retail Customer Management and Segmentation Foundation Segment xml external entity reference
|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.
A vulnerability was found in Oracle Retail Customer Management and Segmentation Foundation 16.0/17.0/18.0/19.0. It has been classified as very critical. This affects some unknown processing of the component Segment. The manipulation with an unknown input leads to a xml external entity vulnerability. CWE is classifying the issue as CWE-611. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
dom4j before 2.0.3 and 2.1.x before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks. However, there is popular external documentation from OWASP showing how to enable the safe, non-default behavior in any application that uses dom4j.
The weakness was published 01/20/2021 as Oracle Critical Patch Update Advisory - January 2021. The advisory is shared at oracle.com. This vulnerability is uniquely identified as CVE-2020-10683 since 03/20/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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 02/17/2021).
We expect the 0-day to have been worth approximately $25k-$100k.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
CVSSv3VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 9.4
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
NVD Base Score: 🔒
ExploitingClass: XML External Entity
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceThreat: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline03/20/2020 CVE assigned
01/20/2021 +306 days Advisory disclosed
01/20/2021 +0 days Countermeasure disclosed
01/20/2021 +0 days VulDB entry created
02/17/2021 +28 days VulDB last update
Advisory: Oracle Critical Patch Update Advisory - January 2021
CVE: CVE-2020-10683 (🔒)
EntryCreated: 01/20/2021 07:47 PM
Updated: 02/17/2021 06:06 PM
Changes: (18) vulnerability_cwe vulnerability_cvss3_nvd_av vulnerability_cvss3_nvd_ac vulnerability_cvss3_nvd_pr vulnerability_cvss3_nvd_ui vulnerability_cvss3_nvd_s vulnerability_cvss3_nvd_c vulnerability_cvss3_nvd_i vulnerability_cvss3_nvd_a vulnerability_cvss2_nvd_av vulnerability_cvss2_nvd_ac vulnerability_cvss2_nvd_au vulnerability_cvss2_nvd_ci vulnerability_cvss2_nvd_ii vulnerability_cvss2_nvd_ai exploit_price_0day vulnerability_cvss2_nvd_basescore vulnerability_cvss3_nvd_basescore
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!