Oracle Retail Xstore Point of Service 17.0.4/18.0.3/19.0.2/20.0.1 Xenvironment path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Oracle Retail Xstore Point of Service 17.0.4/18.0.3/19.0.2/20.0.1 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Xenvironment. Performing a manipulation results in an unknown weakness. This vulnerability is identified as CVE-2021-29425. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in Oracle Retail Xstore Point of Service 17.0.4/18.0.3/19.0.2/20.0.1 (Warehouse Management System Software). This affects an unknown part of the component Xenvironment. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on confidentiality, and integrity.
The weakness was released 07/19/2022 as Oracle Critical Patch Update Advisory - July 2022. The advisory is shared at oracle.com. This vulnerability is uniquely identified as CVE-2021-29425. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
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-2023-1359). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- IBM Operational Decision Manager
- Hitachi Ops Center
- Apache Commons
- Splunk Splunk Enterprise
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: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.8
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: Path traversalCWE: CWE-22
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/30/2021 🔍07/19/2022 🔍
07/19/2022 🔍
07/20/2022 🔍
02/12/2026 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - July 2022
Status: Confirmed
CVE: CVE-2021-29425 (🔍)
GCVE (CVE): GCVE-0-2021-29425
GCVE (VulDB): GCVE-100-204501
CERT Bund: WID-SEC-2023-1359 - Apache Commons: Schwachstelle ermöglicht Offenlegung von Informationen
Entry
Created: 07/20/2022 08:17Updated: 02/12/2026 08:25
Changes: 07/20/2022 08:17 (39), 08/14/2022 14:59 (2), 08/14/2022 15:02 (19), 02/12/2026 08:25 (21)
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.