# CVE-2021-44233: Missing authorization in SAP GRC Access Control

> An authenticated user can escalate privileges in SAP GRC Access Control due to missing authorization checks.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 14 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xv2h-mwv5-j9r3

## What is CVE-2021-44233?

CVE-2021-44233 is a high-severity missing authorization vulnerability in SAP GRC Access Control, published on 14 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP GRC Access Control - versions V1100_700, V1100_731, V1200_750, does not perform necessary authorization checks for an authenticated user, which could lead to escalation of privileges.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Sap Access Control.

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

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

## Is CVE-2021-44233 being exploited?

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

## Other vulnerabilities in SAP GRC Access Control

- [CVE-2022-39801](https://insights.sbomify.com/CVE-2022-39801/): Auth bypass in SAP GRC Access Control Emergency Access Management (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-44233 is a high-severity missing authorization vulnerability in SAP GRC Access Control, 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-44233 in the wild and no public exploit code.

Affected product: SAP GRC Access Control. 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-44233/ (Markdown: https://insights.sbomify.com/CVE-2021-44233/index.md)
```

## Sources

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

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