# CVE-2024-45284: Missing authorization check in SAP Student Life Cycle Management (SLcM)

> An authenticated attacker can bypass authorization checks to access restricted functions, leading to privilege escalation and integrity impact.

- **Severity:** Low 2.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Sep 2024
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-q44j-mpqx-mx83

## What is CVE-2024-45284?

CVE-2024-45284 is a low-severity missing authorization vulnerability in SAP_SE SAP Student Life Cycle Management (SLcM), published on 10 Sep 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

An authenticated attacker with high privilege can use functions of SLCM transactions to which access should be restricted. This may result in an escalation of privileges causing low impact on integrity of the application.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2024-45284 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45284 is a low-severity missing authorization vulnerability in SAP_SE SAP Student Life Cycle Management (SLcM), published on 10 Sep 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-45284 in the wild and no public exploit code.

Affected product: SAP_SE SAP Student Life Cycle Management (SLcM). 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-45284/ (Markdown: https://insights.sbomify.com/CVE-2024-45284/index.md)
```

## Sources

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

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