# CVE-2021-40809: Privilege escalation in n/a

> Attackers can gain incorrect privileges via specific sign-on workflows in Jamf Pro, requiring an upgrade to mitigate.

- **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:** 1 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jvrm-5w3f-73xf

## What is CVE-2021-40809?

CVE-2021-40809 is a high-severity vulnerability in n/a, published on 1 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Jamf Pro before 10.32.0, aka PI-009921. An account can be granted incorrect privileges in response to authentication that uses specific sign-on workflows.

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

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

It affects 1 product.


Products: Jamf Jamf.

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

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

## Is CVE-2021-40809 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-31224](https://insights.sbomify.com/CVE-2023-31224/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-39303](https://insights.sbomify.com/CVE-2021-39303/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2019-17076](https://insights.sbomify.com/CVE-2019-17076/): Deserialization in n/a (critical 9.8)
- [CVE-2018-10465](https://insights.sbomify.com/CVE-2018-10465/): Missing authorization in n/a (high 8.8)
- [CVE-2021-35037](https://insights.sbomify.com/CVE-2021-35037/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-40809 is a high-severity vulnerability in n/a, published on 1 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-40809 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-40809/ (Markdown: https://insights.sbomify.com/CVE-2021-40809/index.md)
```

## Sources

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

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