CVE-2022-22541
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 - versions 420, 430, may allow legitimate users to access information they shouldn't see through relational or OLAP connections. The main impact is the disclosure of company data to people that shouldn't or don't need to have access.
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 BusinessObjects Business Intelligence Platform versions 420 and 430 contain an access control vulnerability where legitimate authenticated users can access data beyond their intended permissions through relational or OLAP connections, resulting in unauthorized disclosure of company data to users who should not have such access.
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= 420= 430CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed SAP BusinessObjects versionAccess the SAP BusinessObjects Central Management Console (CMC) and navigate to the 'About' section, or use the SAP BusinessObjects Installation Manager to view installed version information. Alternatively, check the version from the system information in the CMC homepage.Affected if The installed version is 420 or 430
-
Confirm relational connections exist in the environmentOpen the SAP BusinessObjects CMC and navigate to the 'Relational Connections' folder under 'Universes'. Review the list of published relational connections. Query the CMS system database if direct database access is available to enumerate all connection objects.Affected if Any relational connections are published and available to users
-
Confirm OLAP connections exist in the environmentOpen the SAP BusinessObjects CMC and navigate to the 'OLAP Connections' folder. Review all published OLAP connections. Check for any BEx queries or BW connections configured.Affected if Any OLAP connections are published and available to users
-
Review user permissions on relational and OLAP connectionsIn the CMC, select each relational and OLAP connection object and view the 'User Rights' or 'Security' tab. Check which users and groups have access to these connections and whether row-level security or data access restrictions are properly defined.Affected if Users have access to connections without proper row-level security or authorization restrictions configured
A user is affected if they are running SAP BusinessObjects version 420 or 430 and have relational or OLAP connections configured, particularly if those connections grant users broader data access than intended.
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 when available, and conduct a review of all relational and OLAP connection configurations to ensure proper row-level security and user authorization boundaries are enforced.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22541 — 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-22541 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