BusinessobjectsApplication · Sap

CVE-2019-0289

HIGH · 7.1 CVSS v3.0 Published 2019-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Under certain conditions SAP BusinessObjects Business Intelligence platform (Analysis for OLAP), versions 4.2 and 4.3, allows an attacker to access information which would otherwise be restricted.

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

SAP BusinessObjects BI platform's Analysis for OLAP component (versions 4.2 and 4.3) contains an information disclosure vulnerability allowing unauthorized access to restricted data under certain conditions. This appears to be an access control bypass where the application fails to properly enforce authorization checks, enabling attackers to retrieve information outside their intended permissions.

MitigationApply SAP security patches or security notes addressing CVE-2019-0289. Review and enforce proper access control configurations in Analysis for OLAP, and restrict network exposure of vulnerable SAP BusinessObjects services.

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
BusinessobjectsApplication
Affected:= 4.2= 4.3

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 BusinessObjects installation version
    Access the Central Management Console (CMC) or use the SAP BusinessObjects Lifecycle Management console to view the installed version. Alternatively, check the installation directory or system information for the exact version number.
    Affected if The installed version is exactly 4.2 or exactly 4.3 (no patches applied)
  2. Confirm Analysis for OLAP component is enabled
    Access the CMC and navigate to the Services or Applications management section. Look for Analysis for OLAP in the list of enabled services or check the OLAP connection settings.
    Affected if Analysis for OLAP is listed as active or enabled in the BusinessObjects administration console
  3. Check OLAP service configuration and permissions
    In the CMC, locate the Analysis for OLAP service settings. Review the configured data sources and connection parameters to understand what OLAP systems are accessible.
    Affected if Analysis for OLAP service is configured and connected to any OLAP data sources (even restricted ones)
  4. Review user security assignments for OLAP access
    In the CMC Users or Groups section, examine which users or groups have been assigned rights to Analysis for OLAP. Check for any overly permissive role assignments.
    Affected if Users exist who have access to Analysis for OLAP and the system contains restricted or sensitive data sources

You are affected if SAP BusinessObjects version is exactly 4.2 or 4.3 AND Analysis for OLAP is enabled with access to sensitive data sources, since the vulnerability allows unauthorized access to restricted data through the access control bypass.

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 or security notes addressing CVE-2019-0289. Review and enforce proper access control configurations in Analysis for OLAP, and restrict network exposure of vulnerable SAP BusinessObjects services.

Fix this in Businessobjects Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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