# CVE-2022-24841: Improper Authorization in github.com/fleetdm/fleet

> A team admin can improperly add themselves to other teams, escalating privileges in Fleet instances using the teams feature.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 18 Apr 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-pr2g-j78h-84cr, UBUNTU-CVE-2022-24841

## What is CVE-2022-24841?

CVE-2022-24841 is a medium-severity missing authorization vulnerability in fleetdm fleet, published on 18 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

fleetdm/fleet is an open source device management, built on osquery. All versions of fleet making use of the teams feature are affected by this authorization bypass issue. Fleet instances without teams, or with teams but without restricted team accounts are not affected. In affected versions a team admin can erroneously add themselves as admin, maintainer or observer on other teams. Users are advised to upgrade to version 4.13. There are no known workarounds for this issue.

Weakness: CWE-863 (Incorrect Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2022-24841?

It affects 1 product.


Products: Fleetdm Fleet.

## How do I fix CVE-2022-24841?

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

## Is CVE-2022-24841 being exploited?

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

## Other vulnerabilities in fleetdm fleet

- [CVE-2020-26276](https://insights.sbomify.com/CVE-2020-26276/): SAML authentication vulnerability in Fleet (critical 10.0)
- [CVE-2026-103264](https://insights.sbomify.com/CVE-2026-103264/): Fleet before 4.87.0 Authentication Bypass via Device Identifiers (critical 9.3)
- [CVE-2026-23518](https://insights.sbomify.com/CVE-2026-23518/): Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment (critical 9.3)
- [CVE-2026-26062](https://insights.sbomify.com/CVE-2026-26062/): Fleet server may terminate unexpectedly when handling certain gRPC requests (high 8.7)
- [CVE-2026-26061](https://insights.sbomify.com/CVE-2026-26061/): Fleet's unbounded request body read allows remote Denial of Service (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24841 and fix it if it is affected.

What it is: CVE-2022-24841 is a medium-severity missing authorization vulnerability in fleetdm fleet, published on 18 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-2022-24841 in the wild and no public exploit code.

Affected product: fleetdm fleet. 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-2022-24841/ (Markdown: https://insights.sbomify.com/CVE-2022-24841/index.md)
```

## Sources

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

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