# CVE-2016-3976: SAP NetWeaver Directory Traversal

> Remote attackers can read arbitrary files on SAP NetWeaver AS Java servers via directory traversal in the CrashFileDownloadServlet.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2016
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-jvxp-2488-w24g

## What is CVE-2016-3976?

CVE-2016-3976 is a high-severity path traversal vulnerability in Sap Netweaver Application Server Java, published on 7 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in SAP NetWeaver AS Java 7.1 through 7.5 allows remote attackers to read arbitrary files via a ..\ (dot dot backslash) in the fileName parameter to CrashFileDownloadServlet, aka SAP Security Note 2234971.

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

## Which versions are affected by CVE-2016-3976?

It affects 1 product.


Products: Sap Netweaver Application Server Java.

## How do I fix CVE-2016-3976?

No fix has been published for CVE-2016-3976 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2016-3976 being exploited?

Yes. Attackers have exploited CVE-2016-3976 in the wild since at least 3 Nov 2021.

Public exploit code:

- SAP NetWeaver AS JAVA 7.1 < 7.5 - Directory Traversal (exploitdb)

## Other vulnerabilities in Sap Netweaver Application Server Java

- [CVE-2020-6287](https://insights.sbomify.com/CVE-2020-6287/): SAP NetWeaver Missing Authentication for Critical Function (critical 10.0, exploited in the wild)
- [CVE-2010-5326](https://insights.sbomify.com/CVE-2010-5326/): SAP NetWeaver Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2016-2386](https://insights.sbomify.com/CVE-2016-2386/): SAP NetWeaver SQL Injection (critical 9.8, exploited in the wild)
- [CVE-2017-12637](https://insights.sbomify.com/CVE-2017-12637/): SAP NetWeaver Directory Traversal (high 7.5, exploited in the wild)
- [CVE-2016-9563](https://insights.sbomify.com/CVE-2016-9563/): SAP NetWeaver XML External Entity (XXE) (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-3976 and fix it if it is affected.

What it is: CVE-2016-3976 is a high-severity path traversal vulnerability in Sap Netweaver Application Server Java, published on 7 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2016-3976 in the wild since at least 3 Nov 2021.

Affected product: Sap Netweaver Application Server Java. 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-2016-3976/ (Markdown: https://insights.sbomify.com/CVE-2016-3976/index.md)
```

## Sources

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

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