dbcve.org
Business Intelligence Development WorkbenchApplication · Sap

CVE-2014-8666

MEDIUM · 5.0 CVSS v2.0 Published 2014-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
The User & Server configuration, InfoView refresh, user rights (BI-BIP-ADM) component in SAP Business Intellignece allows remote attackers to obtain audit event details via unspecified vectors.

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 information disclosure vulnerability in SAP Business Intelligence's BI-BIP-ADM component (User & Server configuration, InfoView refresh, user rights). The flaw allows remote attackers to obtain audit event details without proper authorization, exposing sensitive operational information about system usage and administrative actions.

MitigationApply SAP security patches for this vulnerability and review/restrict access controls on the BI-BIP-ADM component to ensure only authorized administrators can view audit event data.

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 Development WorkbenchApplication
Affected:all versions

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
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/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 Business Intelligence installation
    Check for SAP Business Intelligence components on the system. Look for SAP BusinessObjects Business Intelligence platform installations and note the version. In a Windows environment, check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\SAP or look for SAP BusinessObjects directories. On Unix/Linux, check /opt/sap or standard SAP installation paths.
    Affected if The product is SAP Business Intelligence (particularly BusinessObjects) and version cannot be determined or is an unpatched version of the Development Workbench component.
  2. Verify BI-BIP-ADM component accessibility
    The BI-BIP-ADM component handles User & Server configuration in InfoView. Check if the /Admin or /BIADMWEB URL paths in the SAP BusinessObjects web application server are publicly accessible or exposed without authentication. Review the SAP BusinessObjects Central Management Console (CMC) for web application URLs.
    Affected if The BI-BIP-ADM administrative interface is accessible without requiring administrator authentication.
  3. Inspect InfoView configuration settings
    In SAP BusinessObjects, access the Central Management Console (CMC) and navigate to Applications > InfoView. Check the properties and configuration for InfoView/BIADMWEB. Look for settings related to audit event retrieval and refresh functionality.
    Affected if InfoView is configured to allow unauthenticated or improperly authorized access to audit event details through the BI-BIP-ADM component.
  4. Review audit log access controls
    In the SAP BusinessObjects Central Management Console, navigate to Auditing and Monitoring > Auditing views. Check which users and groups have rights to view audit event data. Verify if the Everyone or Anonymous users have been granted access to audit information.
    Affected if Audit event data can be viewed by users without proper administrative privileges, or if access controls permit unauthorized retrieval of audit details.
  5. Check user rights for BI-BIP-ADM
    In the CMC, navigate to Users and Groups, then check the rights assigned to various roles for the BI-BIP-ADM (Admin) application. Look for any default or overly permissive rights that would allow non-administrators to access administrative audit information.
    Affected if Non-administrator accounts have been granted permissions to access audit event data through the BI-BIP-ADM component.

A user is affected if SAP Business Intelligence Development Workbench is installed with unauthenticated or improperly authorized access to the BI-BIP-ADM component allowing exposure of audit event details.

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 SAP security patches for this vulnerability and review/restrict access controls on the BI-BIP-ADM component to ensure only authorized administrators can view audit event data.

Fix this in Business Intelligence Development Workbench Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-8666 — 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-2014-8666 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