# CVE-2024-27901: Directory Traversal vulnerability in SAP Asset Accounting

> High-privileged attackers can exploit path validation flaws in SAP Asset Accounting to compromise confidentiality, integrity, and availability.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2024
- **Updated:** 6 Sep 2024
- **Also known as:** GHSA-jpmf-chch-c98m

## What is CVE-2024-27901?

CVE-2024-27901 is a high-severity path traversal vulnerability in SAP_SE SAP Asset Accounting, published on 9 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SAP Asset Accounting could allow a high privileged attacker to exploit insufficient validation of path information provided by the users and pass it through to the file API's. Thus, causing a considerable impact on confidentiality, integrity and availability of the application.

Weakness: CWE-35 (Path Traversal: '.../...//')

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


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

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

## Is CVE-2024-27901 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-27901 is a high-severity path traversal vulnerability in SAP_SE SAP Asset Accounting, published on 9 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-27901 in the wild and no public exploit code.

Affected product: SAP_SE SAP Asset Accounting. 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-27901/ (Markdown: https://insights.sbomify.com/CVE-2024-27901/index.md)
```

## Sources

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

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