Business Intelligence Promotion Management ApplicationApplication · Sap

CVE-2017-16684

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
SAP Business Intelligence Promotion Management Application, Enterprise 4.10, 4.20, and 4.30, does not perform authentication checks for functionalities that require user identity.

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 · moderate confidence

This is an authentication bypass vulnerability in SAP Business Intelligence Promotion Management Application (versions 4.10, 4.20, and 4.30) where the application fails to perform authentication checks for functionalities that should require user identity verification. This allows unauthenticated attackers to access sensitive functions that should be restricted to authenticated users.

MitigationApply the vendor-provided SAP security patch for this authentication bypass vulnerability. In the interim, restrict network-level access to the affected SAP application using firewall rules and implement additional access control measures at the network perimeter.

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 Intelligence Promotion Management ApplicationApplication
Affected:= 4.10= 4.20= 4.30

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 the installed version of SAP Business Intelligence Promotion Management Application
    Check the SAP BI platform version information through the SAP BI administration console, SAP BI launcher, or the application's about/version page. This is typically found in the SAP BusinessObjects Enterprise XI or BI platform management tools.
    Affected if The installed version is exactly 4.10, 4.20, or 4.30.
  2. Verify if the Promotion Management Application module is deployed
    Confirm whether the Promotion Management Application component is installed and enabled within the SAP Business Intelligence environment. Check the deployed web applications or BI modules.
    Affected if The Promotion Management Application module is present and active in the SAP BI deployment.
  3. Test authentication enforcement on Promotion Management endpoints
    Attempt to access Promotion Management Application URLs or functions without providing valid credentials. Observe whether the application grants access without requiring authentication.
    Affected if The application allows access to Promotion Management functions without any authentication credentials being presented.
  4. Check network exposure of the SAP BI application
    Determine if the SAP Business Intelligence application and its Promotion Management component are accessible from the network. Verify which network segments can reach the application ports.
    Affected if The application is accessible from network locations where unauthenticated users could potentially connect.

A user is affected if they have SAP Business Intelligence Promotion Management Application installed at version 4.10, 4.20, or 4.30, and the application is accessible without requiring authentication credentials.

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

Apply the vendor-provided SAP security patch for this authentication bypass vulnerability. In the interim, restrict network-level access to the affected SAP application using firewall rules and implement additional access control measures at the network perimeter.

Fix this in Business Intelligence Promotion Management Application Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-16684 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