CVE-2020-6247
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, version 4.2, allows an unauthenticated attacker to prevent legitimate users from accessing a service. Using a specially crafted request, the attacker can crash or flood the Central Management Server, thereby impacting system availability.
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 confidenceDenial of service vulnerability in SAP Business Objects Business Intelligence Platform version 4.2 allows unauthenticated attackers to send specially crafted requests that crash or flood the Central Management Server (CMS), preventing legitimate users from accessing the service.
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.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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP BusinessObjects BI Platform versionLocate the installed version of SAP BusinessObjects Business Intelligence Platform. This can typically be found in the SAP BusinessObjects installation directory, in the version info file, or by querying the Central Management Server (CMS) about its version. On Windows, check the About dialog in the CMC (Central Management Console) or the installation logs.Affected if The installed version is exactly 4.2 (version 4.2)
-
Confirm Central Management Server is runningVerify that the Central Management Server (CMS) service is active. In a Windows environment, this appears as a service named 'SAP BusinessObjects BI Platform 4.2 - Central Management Server' or similar. You can also check if the CMS port (default TCP 8080 for HTTP or 8443 for HTTPS) is listening.Affected if CMS service is running and accepting connections
-
Check CMS network exposureDetermine if the CMS port is exposed to untrusted networks. Identify which network interfaces and IP addresses the CMS is bound to. Check firewall rules and network configuration to see if the CMS ports (8080/8443 or custom ports) are accessible from outside the trusted network.Affected if CMS ports are accessible from untrusted or public networks
-
Review CMS logs for crash or flood indicatorsExamine the Central Management Server logs located in the SAP BusinessObjects logging directory for entries indicating crashes, excessive resource consumption, or abnormal request patterns. Look for repeated error messages, timeout errors, or service restarts.Affected if Logs show CMS crashes, excessive resource usage, or abnormal request volumes
A user is affected if they are running SAP BusinessObjects BI Platform version 4.2 with the Central Management Server exposed and accessible to potential attackers.
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 dataApply the relevant SAP security patch for CVE-2020-6247 to the Business Objects 4.2 installation. Implement network-level rate limiting or Web Application Firewall rules as an interim control to mitigate flooding attempts against the CMS endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6247 — 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-6247 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