# CVE-2024-44121: Information Disclosure in SAP S/4 HANA (Statutory Reports)

> An attacker with basic privileges can access restricted internal user data in SAP S/4 HANA Statutory Reports, compromising confidentiality.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 10 Sep 2024
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-j73c-62cp-6vqj

## What is CVE-2024-44121?

CVE-2024-44121 is a medium-severity vulnerability in SAP_SE SAP S/4 HANA (Statutory Reports), published on 10 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Under certain conditions Statutory Reports in SAP S/4 HANA allows an attacker with basic privileges to access information which would otherwise be restricted. The vulnerability could expose internal user data that should remain confidential. It does not impact the integrity and availability of the application

Weakness: CWE-213 (Exposure of Sensitive Information Due to Incompatible Policies)

## Which versions are affected by CVE-2024-44121?


## How do I fix CVE-2024-44121?

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

## Is CVE-2024-44121 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-44121 and fix it if it is affected.

What it is: CVE-2024-44121 is a medium-severity vulnerability in SAP_SE SAP S/4 HANA (Statutory Reports), published on 10 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-44121 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4 HANA (Statutory Reports). 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-2024-44121/ (Markdown: https://insights.sbomify.com/CVE-2024-44121/index.md)
```

## Sources

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

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