# CVE-2021-33706: Missing authorization in InfraBox

> An authenticated user can modify logs in SAP InfraBox due to improper input validation, compromising audit integrity.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 10 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gw7h-9xvm-83qh

## What is CVE-2021-33706?

CVE-2021-33706 is a medium-severity missing authorization vulnerability in SAP SE InfraBox, published on 10 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Due to improper input validation in InfraBox, logs can be modified by an authenticated user.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Sap Infrabox.

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

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

## Is CVE-2021-33706 being exploited?

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

## Other vulnerabilities in SAP SE InfraBox

- [CVE-2021-33668](https://insights.sbomify.com/CVE-2021-33668/): Other in SAP InfraBox (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-33706 is a medium-severity missing authorization vulnerability in SAP SE InfraBox, published on 10 Aug 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-33706 in the wild and no public exploit code.

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

## Sources

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

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