dbcve.org
Businessobjects Business IntelligenceApplication · Sap

CVE-2022-41203

HIGH · 8.8 CVSS v3.1 Published 2022-11-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
In some workflow of SAP BusinessObjects BI Platform (Central Management Console and BI LaunchPad), an authenticated attacker with low privileges can intercept a serialized object in the parameters and substitute with another malicious serialized object, which leads to deserialization of untrusted data vulnerability. This could highly compromise the Confidentiality, Integrity, and Availability of the system.

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 confidence

In SAP BusinessObjects BI Platform (CMC and BI LaunchPad), an authenticated low-privilege attacker can intercept serialized object parameters and substitute them with malicious serialized objects, leading to unsafe deserialization. This allows code execution or further system compromise.

MitigationApply SAP security patches/notes for CVE-2022-41203 when available; until then, restrict access to affected interfaces to minimal necessary users and monitor for deserialization attack patterns.

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 IntelligenceApplication
Affected:= 4.2= 4.3

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

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

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

  1. Identify SAP BusinessObjects BI Platform version
    Check the installed version through SAP BusinessObjects Central Management Console (CMC) About page, or use the SAP BusinessObjects Administration Tool command line (e.g., 'cmdf -version' or check installation directories for version info). Also check SAP Note 3258624 for version confirmation.
    Affected if Installed version is 4.2 or 4.3 (exact versions as listed in affected products)
  2. Confirm CMC interface is exposed
    Verify if the Central Management Console (CMC) web interface is accessible on the server. Check web server configuration or try accessing the CMC URL (typically /BOE/CMC or /CMC).
    Affected if CMC is accessible and version is 4.2 or 4.3
  3. Confirm BI LaunchPad is exposed
    Verify if the BI LaunchPad web interface is accessible on the server. Check web server configuration or try accessing the BI LaunchPad URL (typically /BOE/BI or /BOE/BILaunchPad).
    Affected if BI LaunchPad is accessible and version is 4.2 or 4.3
  4. Check for unsafe deserialization indicators
    Review web application logs and SAP BusinessObjects traces for deserialization patterns. Look for Java deserialization errors, unexpected serialized object handling, or indicators of serialized object injection in HTTP requests to CMC or BI LaunchPad endpoints.
    Affected if Deserialization activity is observed in logs or there are signs of serialized object manipulation in requests

A user is affected if SAP BusinessObjects BI Platform version 4.2 or 4.3 is installed AND either the CMC or BI LaunchPad interface is accessible, as these are the attack vectors for the unsafe deserialization flaw.

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 SAP security patches/notes for CVE-2022-41203 when available; until then, restrict access to affected interfaces to minimal necessary users and monitor for deserialization attack patterns.

Recommended fix Moderate confidence

SAP BusinessObjects BI Platform 4.3 SP01 or higher (or the latest available 4.2/4.3 patch level as specified in the SAP Security Note)

  1. Check the SAP Security Note for CVE-2022-41203 on the SAP Support Portal (support.sap.com) to obtain the specific patch for your BusinessObjects BI Platform version.
  2. Apply the relevant Security Note patch, or alternatively upgrade to a newer version of BusinessObjects BI Platform that includes the security fix.
  3. After applying the patch or upgrade, verify that the Central Management Console and BI LaunchPad are functioning normally.
  4. Test that the deserialization vulnerability is no longer exploitable by the described attack vector.
  5. Ensure all other recommended SAP security patches are applied to maintain overall system security.
Caveat Review SAP's release notes for the target version to check for configuration or functionality changes that may affect existing reports or integrations

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

Fix this in Businessobjects Business Intelligence Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Check whether your project pulls in CVE-2022-41203 — 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-41203 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