# CVE-2024-33006: File upload vulnerability in SAP NetWeaver Application Server ABAP and ABAP Platform

> Unauthenticated attackers can upload malicious files to SAP NetWeaver ABAP servers, leading to complete system compromise when accessed by victims.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 May 2024
- **Updated:** 16 Dec 2025
- **Also known as:** GHSA-rpjh-2px8-r4m7

## What is CVE-2024-33006?

CVE-2024-33006 is a critical vulnerability in SAP_SE SAP NetWeaver Application Server ABAP and ABAP Platform, published on 14 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An unauthenticated attacker can upload a malicious file to the server which when accessed by a victim can allow an attacker to completely compromise system.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2024-33006 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-33006 is a critical vulnerability in SAP_SE SAP NetWeaver Application Server ABAP and ABAP Platform, published on 14 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-33006 in the wild and no public exploit code.

Affected product: SAP_SE SAP NetWeaver Application Server ABAP and ABAP Platform. 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-33006/ (Markdown: https://insights.sbomify.com/CVE-2024-33006/index.md)
```

## Sources

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

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