dbcve.org
Business Warehouse Universal Data IntegrationApplication · Sap

CVE-2017-16685

MEDIUM · 6.1 CVSS v3.0 Published 2017-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-Site Scripting (XSS) vulnerability in SAP Business Warehouse Universal Data Integration. The application fails to properly encode user-controlled inputs before rendering them in web pages, allowing attackers to inject malicious scripts that execute in the context of other users' browsers.

MitigationImplement proper output encoding for all user-supplied data before rendering in HTML contexts, and apply input validation on all user inputs to prevent injection of malicious scripts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Business Warehouse Universal Data IntegrationApplication
Affected:= 7.10= 7.11= 7.20= 7.30= 7.31= 7.40= 7.50

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP BW UDI version
    Access the SAP system via transaction code SE16 or use SAP LMDB (Landscape Management Database) to query the installed version of Universal Data Integration component. Check the SAP system information via SAP transaction 'SM51' or examine the installed software components in SAP SAPMMC console under 'SAP Business Warehouse' components.
    Affected if The installed version matches exactly 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50 as listed in the affected versions.
  2. Verify web application component is enabled
    Check if the Universal Data Integration web module is active by examining SAP ICM (Internet Communication Manager) configuration via transaction SMICM or checking the web service endpoints exposed for UDI functionality.
    Affected if The web interface for Universal Data Integration is exposed and accessible to users.
  3. Locate UDI web application files
    On the SAP application server, navigate to the directory containing UDI web artifacts. Typical paths include /usr/sap/<SID>/<instance>/j2ee/cluster/ or similar. Look for JSP or HTML files related to Universal Data Integration.
    Affected if Web-facing UDI files exist on the server and are accessible via HTTP/HTTPS.
  4. Review HTTP response for unsanitized input reflection
    Using a web browser or HTTP proxy (like Burp Suite), access the Universal Data Integration web interface and submit test input containing characters such as <script>alert('XSS')</script> in query parameters. Observe if these characters are rendered unchanged in the subsequent page response.
    Affected if User-supplied input is reflected in the HTML response without encoding or sanitization.

You are affected if your installed SAP Business Warehouse Universal Data Integration version is exactly one of: 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50 AND the web interface for this component is enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper output encoding for all user-supplied data before rendering in HTML contexts, and apply input validation on all user inputs to prevent injection of malicious scripts.

Fix this in Business Warehouse Universal Data Integration Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-16685 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-16685 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data