CVE-2020-6288
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 · uneditedSAP Business Objects Business Intelligence Platform (Web Intelligence HTML interface) allows an attacker with edit document rights to upload any file (including script files) without proper file format validation leading to Unrestricted upload of file with dangerous type vulnerability. The attacker can modify some formulas and display erroneous content. The server is not affected only the current user browser session, that can easily be closed.
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 confidenceSAP Business Objects Business Intelligence Platform's Web Intelligence HTML interface allows users with edit document rights to upload arbitrary files (including script files) without proper file format validation, enabling modification of formulas and display of erroneous content. The vulnerability stems from missing validation on the file upload functionality.
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= 4.1= 4.2CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP BusinessObjects installationLocate the SAP BusinessObjects Business Intelligence Platform installation directory or check installed programs on the serverAffected if The software is not present on the system, the vulnerability does not apply
-
Determine the installed versionCheck the BusinessObjects version through the Central Configuration Manager (CCM) or look for version information in the installation directoryAffected if The version is 4.1 or 4.2 (exact match to affected versions)
-
Verify Web Intelligence HTML interface is enabledCheck the Web Intelligence HTML interface settings in the Central Management Console (CMC) under Web Intelligence service configurationAffected if The Web Intelligence HTML interface is enabled and accessible to users
-
Confirm user rights configurationReview user and group permissions in the Central Management Console (CMC) to determine which users have Edit Document rights for Web Intelligence documentsAffected if Users or groups possess Edit Document rights on Web Intelligence documents
-
Assess file upload accessibilityAttempt to access the file upload feature within the Web Intelligence HTML interface as a user with edit rights, or inspect the upload functionality configuration in the CMCAffected if The file upload capability in the Web Intelligence HTML interface is accessible to users with edit document rights
A system is affected if it runs SAP BusinessObjects Business Intelligence Platform version 4.1 or 4.2 with the Web Intelligence HTML interface enabled and users have Edit Document rights that allow access to the vulnerable file upload functionality.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict file format validation for uploads in the Web Intelligence HTML interface and restrict edit document rights to only those users who require them. Users can close their browser session to clear the affected session.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6288 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-6288 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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