dbcve.org
Businessobjects Business Intelligence PlatformApplication · Sap

CVE-2020-6312

MEDIUM · 5.4 CVSS v3.1 Published 2020-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 BusinessObjects Business Intelligence Platform (Web Intelligence HTML interface), versions - 4.1, 4.2, allows an attacker with a non-administrative user account that can edit certain web page properties, can modify how a browser processes particular page elements, leading to stored Cross Site Scripting. In certain situations, when a user accesses an affected web page element, the attacker will be able to access or modify metadata for which they are not authorized.

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

Stored Cross-Site Scripting (XSS) vulnerability in SAP BusinessObjects Business Intelligence Platform's Web Intelligence HTML interface (versions 4.1, 4.2). A non-administrative user with privileges to edit certain web page properties can inject malicious scripts by modifying how the browser processes page elements. When other users access the compromised page element, the stored payload executes, potentially allowing unauthorized access or modification of metadata.

MitigationApply the relevant SAP security patch/Note for CVE-2020-6312. Additionally, implement strict input validation and output encoding for web page properties, and consider limiting edit capabilities for non-administrative users on sensitive page elements.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 BI Platform version
    Access the SAP BusinessObjects Central Management Console (CMC) or check the installation directory for the version file. In the CMC, go to 'About' or check the version through the system information in the SAP BusinessObjects Configuration Wizard. Alternatively, check the file 'boe_war_version.info' in the BusinessObjects installation directory or query the CMS database for the version information.
    Affected if The installed version is 4.1 or 4.2 (including any subversions within these major releases).
  2. Confirm Web Intelligence HTML interface is enabled
    Access the SAP BusinessObjects CMC and navigate to 'Applications' management. Check if 'Web Intelligence' application is enabled and running. You can also verify through the 'InfoView' or 'BI Launch Pad' web interface by attempting to access the Web Intelligence reporting interface.
    Affected if Web Intelligence HTML interface is enabled and accessible to users.
  3. Verify user privilege configuration for web page properties
    In the CMC, go to 'Users and Groups' and examine the privileges assigned to non-administrative users. Check if regular users have 'Edit' or 'Modify' permissions on 'Document' or 'Web Intelligence Document' objects, particularly for page element properties. Review the security rights in the 'Rights' section for typical user roles.
    Affected if Non-administrative users have edit/modify privileges on web page elements or document properties.
  4. Inspect Web Intelligence documents for suspicious script injections
    Using the Web Intelligence HTML interface (BI Launch Pad), open Web Intelligence documents and inspect the page element properties. Look for any page elements (reports, charts, tables) that contain HTML/JavaScript code in their property definitions, especially in titles, descriptions, or custom formatting. Check the document structure via the 'Document Structure' panel for any unexpected script tags or event handlers.
    Affected if Any Web Intelligence document contains stored scripts in page element properties that could execute when viewed by other users.

You are affected if your SAP BusinessObjects BI Platform is version 4.1 or 4.2, the Web Intelligence HTML interface is enabled, and non-administrative users have edit privileges on web page elements where malicious scripts could be injected and stored.

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 relevant SAP security patch/Note for CVE-2020-6312. Additionally, implement strict input validation and output encoding for web page properties, and consider limiting edit capabilities for non-administrative users on sensitive page elements.

Fix this in Businessobjects Business Intelligence Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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