dbcve.org
Businessobjects Business Intelligence PlatformApplication · Sap

CVE-2022-29619

MEDIUM · 6.5 CVSS v3.1 Published 2022-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Under certain conditions SAP BusinessObjects Business Intelligence Platform 4.x - versions 420,430 allows user Administrator to view, edit or modify rights of objects it doesn't own and which would otherwise be restricted.

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 · high confidence

This is an authorization bypass vulnerability in SAP BusinessObjects Business Intelligence Platform where the Administrator user can view, edit, or modify rights on objects it doesn't own, bypassing normal access controls. The flaw allows privilege escalation to restricted objects through a broken object-level permission check.

MitigationApply the relevant SAP security patches for this vulnerability and review object-level permissions to ensure proper access controls are enforced according to the principle of least privilege.

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
Businessobjects Business Intelligence PlatformApplication
Affected:= 420= 430

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP BusinessObjects BI Platform version
    In the Central Management Console (CMC), navigate to the 'About' section or check the version information under the SAP BusinessObjects folder in the Windows Start menu, or run the 'wdeploy' command with version flags. Alternatively, check the SAP BusinessObjects installation directory for a version file.
    Affected if The installed version is exactly 420 or exactly 430 (representing 4.20 or 4.30 SP0).
  2. Verify presence of multi-user object ownership
    In the Central Management Console (CMC), navigate to the 'Folders' or 'Objects' management section and list objects. Check if there are objects owned by users other than the built-in Administrator account.
    Affected if Multiple users own objects in the system, creating the condition where the vulnerability could allow unauthorized access to those objects.
  3. Review Administrator account permissions
    In the CMC, go to 'Users and Groups' and select the Administrator account. Review the 'User Security' or 'Rights' assigned to this account, particularly for objects it does not own.
    Affected if The Administrator account has been granted rights to objects it does not own, or the system shows inconsistent permission assignments.
  4. Check for custom security configurations
    In the CMC, navigate to 'Applications' > 'Central Management Server' > 'Security' and review any custom security right definitions or permission overrides that may have been configured.
    Affected if Non-standard or custom security configurations exist that deviate from default SAP BusinessObjects permission behavior.

The environment is affected if SAP BusinessObjects BI Platform version is exactly 4.20 (420) or 4.30 (430), and the system contains objects owned by users other than the Administrator account.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP security patches for this vulnerability and review object-level permissions to ensure proper access controls are enforced according to the principle of least privilege.

Recommended fix Moderate confidence

SAP BusinessObjects BI Platform 4.3 with latest Support Package (SP) and Feature Pack (FP) as listed in the corresponding SAP Security Note

  1. 1. Log in to the SAP One Support Launchpad (launchpad.support.sap.com) with your S-user ID.
  2. 2. Search for the SAP Security Note related to CVE-2022-29619 - this is typically published as a Security Patch Day note by SAP.
  3. 3. Apply the relevant Security Note patch for your specific version (420 or 430) of SAP BusinessObjects Business Intelligence Platform.
  4. 4. After applying the patch, clear the CMS repository cache and restart the SIA (Server Intelligence Agent) to ensure the authorization fixes take effect.
  5. 5. Verify that the fix works by testing that the Administrator user can no longer access objects it doesn't own when those objects have restricted rights.
Caveat Standard SAP patch application carries minimal risk but always test in a development environment first, as with any system modification

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Businessobjects Business Intelligence Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29619 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29619 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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