# CVE-2022-0432: Prototype Pollution in mastodon/mastodon

> Prototype pollution in Mastodon allows attackers to manipulate object prototypes, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Feb 2022
- **Updated:** 2 Aug 2024
- **Also known as:** BIT-mastodon-2022-0432, GHSA-fqq9-f3pw-4cff

## What is CVE-2022-0432?

CVE-2022-0432 is a high-severity vulnerability in mastodon/mastodon, published on 2 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Prototype Pollution in GitHub repository mastodon/mastodon prior to 3.5.0.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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

1 open source package ship an affected version, including mastodon. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mastodon` | Bitnami | All versions | 3.5.0 |

Products: Joinmastodon Mastodon.

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

Upgrade mastodon to 3.5.0 or later.

## Is CVE-2022-0432 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0432 exists.

Public exploit code:

- Mastodon Prototype Pollution Vulnerability (nuclei): http/cves/2022/CVE-2022-0432.yaml

## Other vulnerabilities in mastodon/mastodon

- [CVE-2023-36460](https://insights.sbomify.com/CVE-2023-36460/): Mastodon vulnerable to arbitrary file creation through media attachments (critical 10.0)
- [CVE-2022-2166](https://insights.sbomify.com/CVE-2022-2166/): Improper Restriction of Excessive Authentication Attempts in mastodon/mastodon (critical 9.8)
- [CVE-2022-24307](https://insights.sbomify.com/CVE-2022-24307/): Missing authorization in n/a (critical 9.8)
- [CVE-2018-21018](https://insights.sbomify.com/CVE-2018-21018/): Auth bypass in n/a (critical 9.8)
- [CVE-2024-23832](https://insights.sbomify.com/CVE-2024-23832/): Mastodon Remote user impersonation and takeover (critical 9.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0432 is a high-severity vulnerability in mastodon/mastodon, published on 2 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0432 exists.

Affected packages and fixed versions:
- mastodon (Bitnami): affected all versions; fixed in 3.5.0

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-0432/ (Markdown: https://insights.sbomify.com/CVE-2022-0432/index.md)
```

## Sources

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

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