# CVE-2021-45891: Missing authorization in n/a

> Attackers can escalate privileges in Softwarebuero Zauner ARC because permission checks are performed only on the client side.

- **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:** 5 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rw7c-r2hj-99vq

## What is CVE-2021-45891?

CVE-2021-45891 is a high-severity missing authorization vulnerability in n/a, published on 5 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Softwarebuero Zauner ARC 4.2.0.4., that allows attackers to escalate privileges within the application, since all permission checks are done client-side, not server-side.

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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

It affects 1 product.


Products: Zauner Arc.

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

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

## Is CVE-2021-45891 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-45893](https://insights.sbomify.com/CVE-2021-45893/): Security feature bypass in n/a (high 7.5)
- [CVE-2021-45892](https://insights.sbomify.com/CVE-2021-45892/): Hardcoded credentials in n/a (medium 5.9)
- [CVE-2021-45894](https://insights.sbomify.com/CVE-2021-45894/): Information disclosure in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-45891 is a high-severity missing authorization vulnerability in n/a, published on 5 Apr 2022. 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-45891 in the wild and no public exploit code.

Affected product: n/a. 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-45891/ (Markdown: https://insights.sbomify.com/CVE-2021-45891/index.md)
```

## Sources

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

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