# CVE-2024-42377: Multiple Missing Authorization Check vulnerabilities in SAP Shared Service Framework

> Authenticated non-admin users can insert entries into non-sensitive tables due to missing authorization checks, impacting application 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:** 13 Aug 2024
- **Updated:** 13 Aug 2024
- **Also known as:** GHSA-9gx3-jqv2-vphr

## What is CVE-2024-42377?

CVE-2024-42377 is a medium-severity missing authorization vulnerability in SAP_SE SAP Shared Service Framework, published on 13 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP shared service framework allows an
authenticated non-administrative user to call a remote-enabled function, which
will allow them to insert value entries into a non-sensitive table, causing low
impact on integrity of the application

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Sap Shared Service Framework.

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

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

## Is CVE-2024-42377 being exploited?

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

## Other vulnerabilities in SAP_SE SAP Shared Service Framework

- [CVE-2024-42376](https://insights.sbomify.com/CVE-2024-42376/): Multiple Missing Authorization Check vulnerabilities in SAP Shared Service Framework (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42377 is a medium-severity missing authorization vulnerability in SAP_SE SAP Shared Service Framework, published on 13 Aug 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-42377 in the wild and no public exploit code.

Affected product: SAP_SE SAP Shared Service Framework. 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-42377/ (Markdown: https://insights.sbomify.com/CVE-2024-42377/index.md)
```

## Sources

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

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