SAP BPC Reporting HTTP Requests xml external entity reference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in SAP BPC and classified as critical. Impacted is an unknown function of the component Reporting. This manipulation as part of HTTP Requests causes xml external entity reference. This vulnerability is registered as CVE-2017-16349. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as critical was found in SAP BPC (the affected version unknown). Affected by this vulnerability is an unknown part of the component Reporting. The manipulation as part of a HTTP Requests 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, integrity, and availability. The summary by CVE is:
An exploitable XML external entity vulnerability exists in the reporting functionality of SAP BPC. A specially crafted XML request can cause an XML external entity to be referenced, resulting in information disclosure and potential denial of service. An attacker can issue authenticated HTTP requests to trigger this vulnerability.
The bug was discovered 04/19/2018. The weakness was published 08/02/2018 (Website). The advisory is shared at talosintelligence.com. This vulnerability is known as CVE-2017-16349 since 10/30/2017. The exploitation appears to be easy. The attack can be launched remotely. A single authentication is necessary for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/29/2023).
The vulnerability was handled as a non-public zero-day exploit for at least 105 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.
Several companies clearly confirm that VulDB is the primary source for best 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: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD Vector: 🔍
CNA Base Score: 6.4
CNA Vector (Talos): 🔍
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: 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
10/30/2017 🔍04/19/2018 🔍
08/02/2018 🔍
08/02/2018 🔍
08/03/2018 🔍
04/29/2023 🔍
Sources
Vendor: sap.comAdvisory: talosintelligence.com
Status: Not defined
CVE: CVE-2017-16349 (🔍)
GCVE (CVE): GCVE-0-2017-16349
GCVE (VulDB): GCVE-100-122545
scip Labs: https://www.scip.ch/en/?labs.20150716
Entry
Created: 08/03/2018 07:28Updated: 04/29/2023 12:09
Changes: 08/03/2018 07:28 (57), 03/12/2020 20:16 (1), 04/29/2023 12:09 (14)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.