# CVE-2024-28167: Missing Authorization check in SAP Group Reporting Data Collection (Enter Package Data)

> An authenticated user can modify specific data in SAP Group Reporting Data Collection without proper authorization, leading to privilege escalation and integrity issues.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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:** 9 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-89fv-9763-xj44

## What is CVE-2024-28167?

CVE-2024-28167 is a medium-severity missing authorization vulnerability in SAP_SE SAP Group Reporting Data Collection (Enter Package Data), published on 9 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP Group Reporting Data Collection does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges. On successful exploitation, specific data can be changed via the Enter Package Data app although the user does not have sufficient authorization causing high impact on Integrity of the appliction.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-28167 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28167 is a medium-severity missing authorization vulnerability in SAP_SE SAP Group Reporting Data Collection (Enter Package Data), published on 9 Apr 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-28167 in the wild and no public exploit code.

Affected product: SAP_SE SAP Group Reporting Data Collection (Enter Package Data). 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-28167/ (Markdown: https://insights.sbomify.com/CVE-2024-28167/index.md)
```

## Sources

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

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