# CVE-2022-24961: Missing authorization in n/a

> Portainer Agent allows unauthorized API access if not recently associated with a Portainer instance, bypassing intended authentication controls.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mx58-xr7v-245r

## What is CVE-2022-24961?

CVE-2022-24961 is a critical missing authorization vulnerability in n/a, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Portainer Agent before 2.11.1, an API server can continue running even if not associated with a Portainer instance in the past few days.

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

It affects 1 product.


Products: Portainer Portainer.

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

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

## Is CVE-2022-24961 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16872](https://insights.sbomify.com/CVE-2019-16872/): Missing authorization in n/a (critical 9.9)
- [CVE-2020-24264](https://insights.sbomify.com/CVE-2020-24264/): Missing authorization in n/a (critical 9.8)
- [CVE-2018-19466](https://insights.sbomify.com/CVE-2018-19466/): Information disclosure in n/a (critical 9.8)
- [CVE-2018-19367](https://insights.sbomify.com/CVE-2018-19367/): Auth bypass in n/a (critical 9.8)
- [CVE-2018-12678](https://insights.sbomify.com/CVE-2018-12678/): Server-side request forgery in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24961 is a critical missing authorization vulnerability in n/a, published on 11 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24961 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-2022-24961/ (Markdown: https://insights.sbomify.com/CVE-2022-24961/index.md)
```

## Sources

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

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