CVE-2023-40622
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 (Promotion Management) - versions 420, 430, under certain condition allows an authenticated attacker to view sensitive information which is otherwise restricted. On successful exploitation, the attacker can completely compromise the application causing high impact on confidentiality, integrity, and 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 confidenceSAP BusinessObjects Business Intelligence Platform versions 420 and 430 contain a vulnerability in the Promotion Management component that allows an authenticated attacker to bypass access restrictions and view sensitive information that should be protected. Successful exploitation can lead to complete compromise of the application with critical impact on confidentiality, integrity, and availability.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 versionAccess the SAP BusinessObjects Central Management Console (CMC) and navigate to the 'About' section, or check the version via the SAP BusinessObjects Installation Manager. The version number is typically visible in the CMC login page footer or in the system information page.Affected if The installed version is exactly 420 or exactly 430 (no SP/FP version indicators provided, but the affected versions are listed as =420 and =430 indicating these specific versions)
-
Confirm Promotion Management is accessibleLog into the CMC and verify whether the Promotion Management node is visible in the CMC navigation tree under the 'Promotions' or 'Promotion Management' category. This component is part of the core BI platform.Affected if The Promotion Management interface is accessible and visible within the CMC for the authenticated user session
-
Check Promotion Management permissionsIn the CMC, navigate to 'Promotions' or 'Promotion Management' and review the rights assigned to the user account being tested. Verify if the user has 'View' or higher permissions on promotion objects.Affected if An authenticated user (particularly one without elevated administrative privileges) can access promotion data or view sensitive content that should be restricted based on their assigned permissions
-
Test for unauthorized access to promotion dataWithin the Promotion Management interface, attempt to view or list existing promotions, promotion packages, or promotion history. Observe whether content from other users, other departments, or restricted promotion objects becomes visible.Affected if A standard or low-privilege authenticated user can view promotion content that they should not have access to according to configured rights
-
Review audit logs for Promotion Management accessAccess the SAP BusinessObjects Audit log database or CMC Audit subystem. Query for recent access events on the Promotion Management component. Look for access patterns by non-admin users to promotion objects.Affected if Audit logs show that users without explicit promotion management rights are successfully accessing or viewing promotion content
A user is affected if they are running SAP BusinessObjects Business Intelligence Platform versions 420 or 430 AND have the Promotion Management component accessible to authenticated users who should not have visibility into sensitive promotion data.
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.
dbcve · scopedApply SAP security patches for CVE-2023-40622 when available. Review and restrict user permissions for Promotion Management functionality to enforce least privilege principles until patches are applied.
SAP BusinessObjects BI Platform 430 SP4 or later (latest supported 430.x release)
- 1. Review SAP Security Note #3258601 (or latest related note) for CVE-2023-40622 on the SAP Support Portal (support.sap.com).
- 2. Confirm your current BusinessObjects BI Platform version (420 or 430) by accessing the CMC (Central Management Console) or using the SAP BusinessObjects Diagnostic Tool.
- 3. If running version 420 or 430, plan for upgrade to version 430 SP4 or later (the latest available supported version).
- 4. Schedule upgrade during a maintenance window to minimize business disruption.
- 5. Before upgrading, backup the CMS database and all BOE directories.
- 6. Run the SAP BusinessObjects installer for the target version, selecting 'Upgrade' option.
- 7. After upgrade, verify Promotion Management functionality and confirm users can no longer access restricted content without proper permissions.
- 8. Review user roles and permissions in CMC to ensure least-privilege access is enforced.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40622 — 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-2023-40622 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