Oracle Retail Xstore Point of Service 15.0/16.0/17.0/18.0 Xstore Services resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Oracle Retail Xstore Point of Service 15.0/16.0/17.0/18.0. This affects an unknown function of the component Xstore Services. Performing a manipulation results in resource consumption. This vulnerability is known as CVE-2019-10072. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.
Details
A vulnerability was found in Oracle Retail Xstore Point of Service 15.0/16.0/17.0/18.0 (Warehouse Management System Software). It has been classified as problematic. This affects some unknown functionality of the component Xstore Services. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 04/15/2020 as Oracle Critical Patch Update Advisory - April 2020 as confirmed advisory (Website). The advisory is shared at oracle.com. This vulnerability is uniquely identified as CVE-2019-10072. The exploitability is told to be difficult. It is possible to initiate the attack remotely. The exploitation requires an enhanced level of successful authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Similar entries are available at VDB-136822, VDB-143679, VDB-148986 and VDB-148703. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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.1VulDB Meta Temp Score: 5.1
VulDB Base Score: 3.9
VulDB Temp Score: 3.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 3.9
Vendor Vector (Oracle): 🔍
NVD Base Score: 7.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: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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
03/26/2019 🔍04/15/2020 🔍
04/15/2020 🔍
04/15/2020 🔍
05/07/2025 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - April 2020
Status: Confirmed
CVE: CVE-2019-10072 (🔍)
GCVE (CVE): GCVE-0-2019-10072
GCVE (VulDB): GCVE-100-153645
SecurityFocus: 108874
See also: 🔍
Entry
Created: 04/15/2020 12:43Updated: 05/07/2025 12:15
Changes: 04/15/2020 12:43 (68), 05/26/2024 03:56 (20), 05/07/2025 12:15 (3)
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.