Vulnerability Details : CVE-2017-16685
Cross-Site scripting (XSS) in SAP Business Warehouse Universal Data Integration, from 7.10 to 7.11, 7.20, 7.30, 7.31, 7.40, 7.50, due to insufficient encoding of user controlled inputs.
Vulnerability category: Cross site scripting (XSS)
Products affected by CVE-2017-16685
- cpe:2.3:a:sap:business_warehouse_universal_data_integration:7.10:*:*:*:*:*:*:*
- cpe:2.3:a:sap:business_warehouse_universal_data_integration:7.20:*:*:*:*:*:*:*
- cpe:2.3:a:sap:business_warehouse_universal_data_integration:7.31:*:*:*:*:*:*:*
- cpe:2.3:a:sap:business_warehouse_universal_data_integration:7.40:*:*:*:*:*:*:*
- cpe:2.3:a:sap:business_warehouse_universal_data_integration:7.50:*:*:*:*:*:*:*
- cpe:2.3:a:sap:business_warehouse_universal_data_integration:7.11:*:*:*:*:*:*:*
- cpe:2.3:a:sap:business_warehouse_universal_data_integration:7.30:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2017-16685
0.12%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 45 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2017-16685
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
4.3
|
MEDIUM | AV:N/AC:M/Au:N/C:N/I:P/A:N |
8.6
|
2.9
|
NIST | |
6.1
|
MEDIUM | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
2.8
|
2.7
|
NIST |
CWE ids for CVE-2017-16685
-
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.Assigned by: nvd@nist.gov (Primary)
References for CVE-2017-16685
-
https://launchpad.support.sap.com/#/notes/2537545
SAP ONE Support Launchpad: Log OnPermissions Required
-
http://www.securityfocus.com/bid/102148
SAP BW Universal Data Integration CVE-2017-16685 Cross Site Scripting VulnerabilityThird Party Advisory;VDB Entry
-
https://blogs.sap.com/2017/12/12/sap-security-patch-day-december-2017/
SAP Security Patch Day – December 2017 | SAP BlogsVendor Advisory
Jump to