Oracle Retail Predictive Application Server 15.0.3 RPAS Fusion Client xml external entity reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Oracle Retail Predictive Application Server 15.0.3. The affected element is an unknown function of the component RPAS Fusion Client. This manipulation causes xml external entity reference. This vulnerability is tracked as CVE-2019-12415. The attack is restricted to local execution. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Oracle Retail Predictive Application Server 15.0.3 (Application Server Software). It has been declared as critical. Affected by this vulnerability is an unknown code of the component RPAS Fusion Client. The manipulation with an unknown input 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.
The weakness was disclosed 01/15/2020 as Oracle Critical Patch Update Advisory - January 2020 as confirmed advisory (Website). The advisory is shared at oracle.com. This vulnerability is known as CVE-2019-12415. An attack has to be approached locally. A single authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-0143). The entries VDB-144093, VDB-149016, VDB-149015 and VDB-149014 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Oracle Fusion Middleware
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 5.5
Vendor Vector (Oracle): 🔍
NVD Base Score: 5.5
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: Partially
Local: Yes
Remote: No
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
05/28/2019 🔍01/15/2020 🔍
01/15/2020 🔍
01/16/2020 🔍
08/18/2025 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - January 2020
Status: Confirmed
CVE: CVE-2019-12415 (🔍)
GCVE (CVE): GCVE-0-2019-12415
GCVE (VulDB): GCVE-100-148957
CERT Bund: WID-SEC-2025-0143 - Oracle Fusion Middleware: Mehrere Schwachstellen
See also: 🔍
Entry
Created: 01/16/2020 08:10Updated: 08/18/2025 14:08
Changes: 01/16/2020 08:10 (52), 01/16/2020 09:02 (16), 03/23/2024 18:14 (19), 08/18/2025 14:08 (7)
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.