# CVE-2023-27894: Sensitive Information Disclosure in the SAP BusinessObjects Business Intelligence platform

> Attackers can inject CMS parameters to scan internal networks and retrieve server files, leading to sensitive information disclosure in SAP BusinessObjects.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **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:** 14 Mar 2023
- **Updated:** 27 Feb 2025
- **Also known as:** GHSA-w7jv-qf6x-vrwr

## What is CVE-2023-27894?

CVE-2023-27894 is a medium-severity server-side request forgery vulnerability in SAP BusinessObjects Business Intelligence Platform (Web Services), published on 14 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP BusinessObjects Business Intelligence Platform (Web Services) - versions 420, 430, allows an attacker to inject arbitrary values as CMS parameters to perform lookups on the internal network which is otherwise not accessible externally. On successful exploitation, attacker can scan internal network to determine internal infrastructure for further attacks like remote file inclusion, retrieve server files, bypass firewall and force the vulnerable server to execute malicious requests, resulting in sensitive information disclosure. This causes limited impact on confidentiality of data.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Sap Businessobjects Business Intelligence.

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

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

## Is CVE-2023-27894 being exploited?

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

## Other vulnerabilities in SAP BusinessObjects Business Intelligence Platform (Web Services)

- [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-2022-41203](https://insights.sbomify.com/CVE-2022-41203/): Deserialization in SAP BusinessObjects Business Intelligence Platform (Central Management Console and BI Launchpad) (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-27894 is a medium-severity server-side request forgery vulnerability in SAP BusinessObjects Business Intelligence Platform (Web Services), published on 14 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-27894 in the wild and no public exploit code.

Affected product: SAP BusinessObjects Business Intelligence Platform (Web Services). 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-2023-27894/ (Markdown: https://insights.sbomify.com/CVE-2023-27894/index.md)
```

## Sources

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

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