CVE-2021-40500
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 BusinessObjects Business Intelligence Platform (Crystal Reports) - versions 420, 430, allows an unauthenticated attacker to exploit missing XML validations at endpoints to read sensitive data. These endpoints are normally exposed over the network and successful exploitation can enable the attacker to retrieve arbitrary files from the server.
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 confidenceUnauthenticated XML validation vulnerability in SAP BusinessObjects Business Intelligence Platform (Crystal Reports) versions 420 and 430 allows attackers to exploit missing XML validation at network-exposed endpoints to read arbitrary files from the server.
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.20= 4.30CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installation and versionLocate the SAP BusinessObjects installation directory (commonly at C:\Program Files\SAP BusinessObjects\ or /opt/sap businessobjects/). Check the version.info or about screen in the Central Management Console (CMC). In the CMC, navigate to About or check the version through the help menu.Affected if The installed version is exactly 4.20 or 4.30
-
Locate network-exposed Crystal Reports endpointsReview web server configuration (Apache Tomcat or SAP BusinessObjects Tomcat bundled server). Common paths include: {SAP_BOE_HOME}\tomcat\webapps\crystalservices\ or similar endpoints under the BOE war deployment. Check for .jsp or .do endpoints that handle XML input.Affected if The Crystal Reports web services are exposed on network-accessible ports (default 8080 or 443)
-
Confirm XML processing is enabled on affected endpointsExamine the web.xml deployment descriptor in the Tomcat conf directory under the BOE application. Look for XML-related servlet mappings (often related to ReportViewer or XMLAPI services). Check if the XML validator servlet is present and loaded.Affected if XML processing servlets are mapped and loaded in the web application context accessible via HTTP/HTTPS
You are affected if you run BusinessObjects version 4.20 or 4.30 with Crystal Reports web services exposed to the network and XML endpoints are accessible without authentication.
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 available SAP security patches for CVE-2021-40500 and implement network segmentation to restrict access to affected endpoints until patching is complete.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-40500 — 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-2021-40500 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