Oracle Retail Integration Bus 15.0.3 RIB Kernal server-side request forgery
|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 Integration Bus 15.0.3. It has been classified as critical. Affected is an unknown functionality of the component RIB Kernal. The manipulation with an unknown input leads to a privilege escalation vulnerability. CWE is classifying the issue as CWE-918. This is going to have an impact on integrity. CVE summarizes:
Apache Batik is vulnerable to server-side request forgery, caused by improper input validation by the "xlink:href" attributes. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests.
The weakness was shared 01/20/2021 as Oracle Critical Patch Update Advisory - January 2021. The advisory is available at oracle.com. This vulnerability is traded as CVE-2019-17566 since 10/14/2019. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 02/17/2021).
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
CVSSv3VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
NVD Base Score: 🔒
ExploitingClass: Privilege escalation
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceThreat: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline10/14/2019 CVE assigned
01/20/2021 +464 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-2019-17566 (🔒)
EntryCreated: 01/20/2021 07:48 PM
Updated: 02/17/2021 07:27 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!