| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as critical has been found in SAP POS. Affected by this issue is some unknown functionality of the component Xpress Server. This manipulation causes access control. This vulnerability is handled as CVE-2017-15295. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as critical was found in SAP POS (version now known). Affected by this vulnerability is some unknown processing of the component Xpress Server. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Xpress Server in SAP POS does not require authentication for read/write/delete file access. This is SAP Security Note 2520064.
The bug was discovered 09/12/2017. The weakness was released 10/16/2017 (Website). It is possible to read the advisory at blogs.sap.com. This vulnerability is known as CVE-2017-15295 since 10/12/2017. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 11/25/2019). The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 34 days. During that time the estimated underground price was around $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entry connected to this vulnerability is available at VDB-106757. Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
License
Website
- Vendor: https://www.sap.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.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: Access controlCWE: CWE-264
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/12/2017 🔍10/12/2017 🔍
10/16/2017 🔍
10/16/2017 🔍
10/17/2017 🔍
11/25/2019 🔍
Sources
Vendor: sap.comAdvisory: blogs.sap.com
Status: Not defined
CVE: CVE-2017-15295 (🔍)
GCVE (CVE): GCVE-0-2017-15295
GCVE (VulDB): GCVE-100-107911
scip Labs: https://www.scip.ch/en/?labs.20150716
See also: 🔍
Entry
Created: 10/17/2017 09:06Updated: 11/25/2019 13:13
Changes: 10/17/2017 09:06 (57), 11/25/2019 13:13 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.

No comments yet. Languages: en.
Please log in to comment.