dbcve.org
Businessobjects Business Intelligence PlatformApplication · Sap

CVE-2020-6195

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-14
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 (CMC), version 4.1, 4.2, shows cleartext password in the response, leading to Information Disclosure. It involves social engineering in order to gain access to system and If password is known, it would give administrative rights to the attacker to read/modify delete the data and rights within the system.

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

The vulnerability allows the SAP Business Objects Central Management Console (CMC) to return cleartext passwords in HTTP responses. This information disclosure occurs when users access certain CMC functions, exposing administrative credentials that can then be used to gain full administrative access to the platform.

MitigationApply the relevant SAP security patch for CVE-2020-6195. Until then, monitor CMC access logs for unusual administrative activity and restrict network access to the CMC interface to limit exposure to social engineering attacks.

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:= 4.1= 4.2

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 SAP BusinessObjects BI Platform version
    Locate the installed version of SAP BusinessObjects Business Intelligence Platform through the SAP BusinessObjects installer, SAP LM, or the Central Configuration Manager (CCM) tool typically found in the installation directory
    Affected if The installed version is 4.1 or 4.2 (any subversion within these release lines)
  2. Confirm the Central Management Console (CMC) is deployed
    Verify that the CMC web application is deployed and accessible on the server by checking the SAP BusinessObjects web application server (such as Tomcat) for the CMC war file or checking if the CMC URL is reachable
    Affected if The CMC interface is deployed and accessible to users
  3. Capture and inspect CMC HTTP responses
    Use a web proxy, browser developer tools, or network packet capture to intercept HTTP responses when accessing CMC functions (such as user management, authentication, or system configuration pages)
    Affected if HTTP responses from CMC contain cleartext passwords instead of masked or hashed values for administrative or user accounts

You are affected if you have SAP BusinessObjects Business Intelligence Platform version 4.1 or 4.2 with the CMC interface accessible, and HTTP responses from CMC functions expose credentials in cleartext form.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patch for CVE-2020-6195. Until then, monitor CMC access logs for unusual administrative activity and restrict network access to the CMC interface to limit exposure to social engineering attacks.

Recommended fix Moderate confidence

SAP BusinessObjects BI Platform 4.3 (or latest 4.2 patch per SAP Security Note)

  1. Check the current SAP BusinessObjects BI Platform version via the Central Management Console (CMC) / About section
  2. Review SAP Security Note 2998175 (or the relevant note for CVE-2020-6195) on the SAP Support Portal
  3. If on 4.1: Plan upgrade path to BusinessObjects BI Platform 4.2 or later
  4. If on 4.2: Apply the latest available patch for version 4.2 that addresses this vulnerability, or upgrade to BusinessObjects BI Platform 4.3
  5. After upgrade/patch, verify the fix by checking that passwords are no longer transmitted in cleartext in CMC responses
  6. Validate that administrative accounts can still authenticate properly after the change
Caveat Review SAP release notes for version 4.3 for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Businessobjects Business Intelligence Platform 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-2020-6195 — 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-6195 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