dbcve.org
Businessobjects Business Intelligence PlatformApplication · Sap

CVE-2020-6242

CRITICAL · 9.8 CVSS v3.1 Published 2020-05-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 Objects Business Intelligence Platform (Live Data Connect), versions 1.0, 2.0, 2.1, 2.2, 2.3, allows an attacker to logon on the Central Management Console without password in case of the BIPRWS application server was not protected with some specific certificate, leading to Missing Authentication Check.

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

SAP Business Objects Live Data Connect versions 1.0-2.3 contains a missing authentication check in the Central Management Console (CMC). When the BIPRWS application server is not protected with a specific certificate, an attacker can bypass authentication entirely and logon to the CMC without providing any password, gaining full administrative access to the BI platform.

MitigationEnsure the BIPRWS application server is properly protected with the required specific certificate and enforce certificate-based authentication for all CMC access points.

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
Businessobjects Business Intelligence PlatformApplication
Affected:= 1.0= 2.0= 2.1= 2.2= 2.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/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 Live Data Connect version
    Check the SAP BusinessObjects Business Intelligence Platform version by examining the installed software components. In the SAP BI platform, verify the Live Data Connect version through the Central Management Console (CMC) About section, or check the installation directory for version information.
    Affected if The installed version is 1.0, 2.0, 2.1, 2.2, or 2.3.
  2. Locate the BIPRWS application server configuration
    Identify the BIPRWS (BusinessObjects Predictive Insights or BI Platform RESTful Web Services) application server configuration in your SAP BusinessObjects deployment. Check the web server or SAP NetWeaver configuration files where BIPRWS is deployed.
    Affected if BIPRWS is present in the environment.
  3. Verify certificate protection on BIPRWS
    Examine the BIPRWS application server configuration to determine whether it is configured with the required specific certificate for authentication. Check the SSL/TLS configuration, server.xml, or equivalent web server configuration files for certificate binding.
    Affected if BIPRWS is NOT protected with the required specific certificate, or no certificate-based authentication is configured.
  4. Check CMC authentication settings
    Access the Central Management Console (CMC) authentication configuration. Navigate to the Authentication settings within CMC to review how authentication is enforced for CMC access.
    Affected if CMC authentication settings allow access without certificate-based verification when BIPRWS lacks certificate protection.

A user is affected if they run any Live Data Connect version 1.0-2.3 AND the BIPRWS application server is not protected with the required certificate, allowing unauthenticated CMC access.

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

Ensure the BIPRWS application server is properly protected with the required specific certificate and enforce certificate-based authentication for all CMC access points.

Fix this in Businessobjects Business Intelligence Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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