# CVE-2024-4139: Missing Authorization Checks in SAP S/4 HANA (Manage Bank Statement Reprocessing Rules)

> An authenticated attacker can delete other users' bank statement reprocessing rules due to missing authorization checks, compromising data integrity.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-3wpq-gjx8-r7c8

## What is CVE-2024-4139?

CVE-2024-4139 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4 HANA (Manage Bank Statement Reprocessing Rules), published on 14 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Manage Bank Statement ReProcessing Rules does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges. By exploiting this vulnerability, an attacker can delete rules of other users affecting the integrity of the application. Confidentiality and Availability are not affected.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-4139 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4139 is a medium-severity missing authorization vulnerability in SAP_SE SAP S/4 HANA (Manage Bank Statement Reprocessing Rules), published on 14 May 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-4139 in the wild and no public exploit code.

Affected product: SAP_SE SAP S/4 HANA (Manage Bank Statement Reprocessing Rules). 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-4139/ (Markdown: https://insights.sbomify.com/CVE-2024-4139/index.md)
```

## Sources

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

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