# CVE-2024-47576: DLL Hijacking vulnerability in SAP Product Lifecycle Costing

> Attackers can execute arbitrary code by replacing a DLL loaded by the SAP Product Lifecycle Costing Client application.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2024
- **Updated:** 10 Dec 2024
- **Also known as:** GHSA-v99m-rxjx-rq75

## What is CVE-2024-47576?

CVE-2024-47576 is a low-severity vulnerability in SAP_SE SAP Product Lifecycle Costing, published on 10 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SAP Product Lifecycle Costing Client (versions below 4.7.1) application loads on demand a DLL that is available with Windows OS. This DLL is loaded from the computer running SAP Product Lifecycle Costing Client application. That particular DLL could be replaced by a malicious one, that could execute commands as being part of SAP Product Lifecycle Costing Client Application. On a successful attack, it can cause a low impact to confidentiality but no impact to the integrity and availability of the application.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2024-47576 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47576 is a low-severity vulnerability in SAP_SE SAP Product Lifecycle Costing, published on 10 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47576 in the wild and no public exploit code.

Affected product: SAP_SE SAP Product Lifecycle Costing. 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-47576/ (Markdown: https://insights.sbomify.com/CVE-2024-47576/index.md)
```

## Sources

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

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