Oracle Primavera Unifier up to 20.12 jackson-databind 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 classified as problematic has been found in Oracle Primavera Unifier up to 20.12 (Asset Management Software). Affected is an unknown part of the component jackson-databind. 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, and integrity. CVE summarizes:
A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly. This flaw allows vulnerability to XML external entity (XXE) attacks. The highest threat from this vulnerability is data integrity.
The weakness was presented 07/20/2021 as Oracle Critical Patch Update Advisory - July 2021. The advisory is shared for download at oracle.com. This vulnerability is traded as CVE-2020-25649 since 09/16/2020. The exploitability is told to be easy. The attack needs to be approached locally. A authentication is necessary for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
CVSSv3VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.6
VulDB Base Score: 3.9
VulDB Temp Score: 3.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
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 IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline09/16/2020 CVE assigned
07/20/2021 +307 days Advisory disclosed
07/20/2021 +0 days Countermeasure disclosed
07/21/2021 +1 days VulDB entry created
07/23/2021 +2 days VulDB last update
Advisory: Oracle Critical Patch Update Advisory - July 2021
CVE: CVE-2020-25649 (🔒)
EntryCreated: 07/21/2021 10:36 AM
Updated: 07/23/2021 02:53 PM
Changes: (20) vulnerability_cwe vulnerability_cvss2_nvd_basescore vulnerability_cvss2_nvd_av vulnerability_cvss2_nvd_ac vulnerability_cvss2_nvd_au vulnerability_cvss2_nvd_ci vulnerability_cvss2_nvd_ii vulnerability_cvss2_nvd_ai vulnerability_cvss3_meta_basescore vulnerability_cvss3_meta_tempscore vulnerability_cvss3_nvd_basescore 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 exploit_price_0day
Do you want to use VulDB in your project?
Use the official API to access entries easily!