# CVE-2022-41203: Deserialization in SAP BusinessObjects Business Intelligence Platform (Central Management Console and BI Launchpad)

> An authenticated low-privilege attacker can exploit deserialization of untrusted data in SAP BusinessObjects BI to compromise system confidentiality, integrity, and availability.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Nov 2022
- **Updated:** 1 May 2025
- **Also known as:** GHSA-733v-x8pr-2mxj

## What is CVE-2022-41203?

CVE-2022-41203 is a critical unsafe deserialization vulnerability in SAP BusinessObjects Business Intelligence Platform (Central Management Console and BI Launchpad), published on 8 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2022-41203?

It affects 1 product.


Products: Sap Businessobjects Business Intelligence.

## How do I fix CVE-2022-41203?

No fix has been published for CVE-2022-41203 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-41203 being exploited?

There is no known exploitation of CVE-2022-41203 in the wild and no public exploit code.

## Other vulnerabilities in SAP BusinessObjects Business Intelligence Platform (Central Management Console and BI Launchpad)

- [CVE-2023-40622](https://insights.sbomify.com/CVE-2023-40622/): Information Disclosure vulnerability in SAP BusinessObjects Business Intelligence Platform (Promotion Management) (critical 9.9)
- [CVE-2023-28765](https://insights.sbomify.com/CVE-2023-28765/): Information Disclosure vulnerability in SAP BusinessObjects Business Intelligence Platform (Promotion Management ) (critical 9.8)
- [CVE-2018-2445](https://insights.sbomify.com/CVE-2018-2445/): Server-side request forgery in SAP BusinessObjects Business Intelligence Platform (critical 9.6)
- [CVE-2023-28762](https://insights.sbomify.com/CVE-2023-28762/): Information Disclosure in SAP BusinessObjects Intelligence Platform (critical 9.1)
- [CVE-2018-2442](https://insights.sbomify.com/CVE-2018-2442/): Cross-site request forgery in SAP BusinessObjects Business Intelligence (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41203 and fix it if it is affected.

What it is: CVE-2022-41203 is a critical unsafe deserialization vulnerability in SAP BusinessObjects Business Intelligence Platform (Central Management Console and BI Launchpad), published on 8 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41203 in the wild and no public exploit code.

Affected product: SAP BusinessObjects Business Intelligence Platform (Central Management Console and BI Launchpad). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-41203/ (Markdown: https://insights.sbomify.com/CVE-2022-41203/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-41203
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-41203
- OSV: https://osv.dev/vulnerability/CVE-2022-41203

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-41203/
Summaries are generated and may contain mistakes; the official description above is the record.