CVE-2022-28216
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 (BI Workspace) - version 420, is susceptible to a Cross-Site Scripting attack by an unauthenticated attacker due to improper sanitization of the user inputs on the network. On successful exploitation, an attacker can access certain reports causing a limited impact on confidentiality of the application data.
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 confidenceCross-Site Scripting (XSS) vulnerability in SAP BusinessObjects BI Workspace version 420 allows unauthenticated attackers to inject malicious scripts through improperly sanitized user inputs. Successful exploitation enables access to certain reports with limited confidentiality impact.
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= 420CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SAP BusinessObjects BI Platform installationLocate the SAP BusinessObjects installation directory or check running services for BusinessObjects processes (e.g., 'Tomcat' or 'Java' processes serving BusinessObjects). Use SAP Administration tools or check for BI Platform client tools if available.Affected if SAP BusinessObjects Business Intelligence Platform is not installed or running.
-
Verify installed version is 420Check the installed version of SAP BusinessObjects BI Platform through the SAP Central Management Console (CMC), SAP BI Launch Pad, or by inspecting version information in the installation directory or registry if on Windows. Compare against the affected version 420.Affected if The installed version is exactly 420.
-
Confirm BI Workspace module is enabledAccess the SAP BI Workspace interface through the web browser (typically at /BOE/BI or /BILaunchPad) or check via SAP CMC to see if the BI Workspace application module is deployed and accessible.Affected if BI Workspace module is deployed and accessible to users.
-
Check network exposure of BI WorkspaceDetermine if the BI Workspace web interface is exposed to unauthenticated or external network access by reviewing web server configuration, load balancer settings, or firewall rules governing the BusinessObjects web application.Affected if BI Workspace is accessible without authentication or from untrusted networks.
A user is affected if SAP BusinessObjects BI Platform version 420 is running with the BI Workspace module enabled and accessible, as this version contains the unsanitized user input vulnerability in BI Workspace.
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 SAP security patches for CVE-2022-28216 and implement proper input validation and output encoding for all user-supplied data in BI Workspace.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2022-28216 — 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-2022-28216 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