# CVE-2021-44232: Path traversal in SAF-T Framework

> An attacker can exploit insufficient path validation in the SAP SAF-T Framework to read the entire server filesystem structure.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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:** 14 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4g5h-vp8c-mrhf

## What is CVE-2021-44232?

CVE-2021-44232 is a high-severity path traversal vulnerability in SAP SE SAF-T Framework, published on 14 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAF-T Framework Transaction SAFTN_G allows an attacker to exploit insufficient validation of path information provided by normal user, leading to full server directory access. The attacker can see the whole filesystem structure but cannot overwrite, delete, or corrupt arbitrary files on the server.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2021-44232?

It affects 1 product.


Products: Sap Saf-T Framework.

## How do I fix CVE-2021-44232?

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

## Is CVE-2021-44232 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-44232 and fix it if it is affected.

What it is: CVE-2021-44232 is a high-severity path traversal vulnerability in SAP SE SAF-T Framework, published on 14 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-44232 in the wild and no public exploit code.

Affected product: SAP SE SAF-T 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-2021-44232/ (Markdown: https://insights.sbomify.com/CVE-2021-44232/index.md)
```

## Sources

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

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