# CVE-2021-33690: Server-side request forgery in SAP NetWeaver Development Infrastructure (Component Build Service)

> An attacker with server access can perform SSRF attacks to compromise sensitive data and impact availability in SAP NetWeaver NWDI.

- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 15 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-76pj-fv2h-qvfg

## What is CVE-2021-33690?

CVE-2021-33690 is a critical server-side request forgery vulnerability in SAP NetWeaver Development Infrastructure (Component Build Service), published on 15 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) vulnerability has been detected in the SAP NetWeaver Development Infrastructure Component Build Service versions - 7.11, 7.20, 7.30, 7.31, 7.40, 7.50The SAP NetWeaver Development Infrastructure Component Build Service allows a threat actor who has access to the server to perform proxy attacks on server by sending crafted queries. Due to this, the threat actor could completely compromise sensitive data residing on the Server and impact its availability.Note: The impact of this vulnerability depends on whether SAP NetWeaver Development Infrastructure (NWDI) runs on the intranet or internet. The CVSS score reflects the impact considering the worst-case scenario that it runs on the internet.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Sap Netweaver Development Infrastructure.

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

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

## Is CVE-2021-33690 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-33690 exists.

Public exploit code:

- [CVE-2021-33690] Server Side Request Forgery vulnerability in SAP NetWeaver Development Infrastructure (github_poc): https://github.com/redrays-io/CVE-2021-33690
- SAP NetWeaver Development Infrastructure - Server Side Request Forgery (nuclei): http/cves/2021/CVE-2021-33690.yaml

## Other vulnerabilities in SAP NetWeaver Development Infrastructure (Component Build Service)

- [CVE-2013-6820](https://insights.sbomify.com/CVE-2013-6820/): File upload in n/a (critical 9.3)
- [CVE-2021-33691](https://insights.sbomify.com/CVE-2021-33691/): Cross-site scripting in SAP NetWeaver Development Infrastructure (Notification Service) (medium 6.9)
- [CVE-2022-29618](https://insights.sbomify.com/CVE-2022-29618/): Cross-site scripting in SAP NetWeaver Development Infrastructure (Design Time Repository) (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-33690 is a critical server-side request forgery vulnerability in SAP NetWeaver Development Infrastructure (Component Build Service), published on 15 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-33690 exists.

Affected product: SAP NetWeaver Development Infrastructure (Component Build Service). 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-33690/ (Markdown: https://insights.sbomify.com/CVE-2021-33690/index.md)
```

## Sources

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

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