# CVE-2023-25617: OS Command Execution vulnerability in SAP Business Objects Business Intelligence Platform (Adaptive Job Server)

> Authenticated users with scheduling rights can execute arbitrary OS commands on Unix systems via the Adaptive Job Server.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Mar 2023
- **Updated:** 27 Feb 2025
- **Also known as:** GHSA-xxhh-59gh-6ffx, PYSEC-2023-315

## What is CVE-2023-25617?

CVE-2023-25617 is a critical command injection vulnerability in SAP Business Objects (Adaptive Job Server), published on 14 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

SAP Business Object (Adaptive Job Server) - versions 420, 430, allows remote execution of arbitrary commands on Unix, when program objects execution is enabled, to authenticated users with scheduling rights, using the BI Launchpad, Central Management Console or a custom application based on the public java SDK. Programs could impact the confidentiality, integrity and availability of the system.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2023-25617?

3 open source packages ship an affected version, including sap-ai-sdk-base. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sap-ai-sdk-base` | PyPI | All versions to 3.3.0 | None |
| `sap-ai-sdk-base` | PyPI | All versions to 3.3.0 | None |
| `sap-ai-sdk-base` | PyPI | All versions to 420 | None |

Products: Sap Business Objects Business Intelligence Platform.

## How do I fix CVE-2023-25617?

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

## Is CVE-2023-25617 being exploited?

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

## Other vulnerabilities in SAP Business Objects (Adaptive Job Server)

- [CVE-2023-25616](https://insights.sbomify.com/CVE-2023-25616/): Code Injection vulnerability in SAP Business Objects Business Intelligence Platform (CMC) (critical 9.9)
- [CVE-2022-41267](https://insights.sbomify.com/CVE-2022-41267/): File upload in BusinessObjects Business Intelligence Platform (critical 9.9)
- [CVE-2024-41730](https://insights.sbomify.com/CVE-2024-41730/): Missing Authentication check in SAP BusinessObjects Business Intelligence Platform (critical 9.8)
- [CVE-2022-39013](https://insights.sbomify.com/CVE-2022-39013/): Information disclosure in SAP BusinessObjects Business Intelligence Platform (Program Objects) (high 7.6)
- [CVE-2023-42478](https://insights.sbomify.com/CVE-2023-42478/): Cross-Site Scripting (XSS) vulnerability in SAP BusinessObjects Business Intelligence Platform (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25617 and fix it if it is affected.

What it is: CVE-2023-25617 is a critical command injection vulnerability in SAP Business Objects (Adaptive Job Server), published on 14 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-25617 in the wild and no public exploit code.

Affected packages and fixed versions:
- sap-ai-sdk-base (PyPI): affected all versions up to 3.3.0; no fix listed
- sap-ai-sdk-base (PyPI): affected all versions up to 3.3.0; no fix listed
- sap-ai-sdk-base (PyPI): affected all versions up to 420; no fix listed

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-2023-25617/ (Markdown: https://insights.sbomify.com/CVE-2023-25617/index.md)
```

## Sources

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

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