# CVE-2022-29180: Charm vulnerable to server-side request forgery (SSRF)

> Attackers can forge HTTP requests to manipulate the Charm data directory, allowing access to or deletion of server files.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/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:** Yes
- **Published:** 7 May 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-4wpp-w5r4-7v5v, GO-2022-0449

## What is CVE-2022-29180?

CVE-2022-29180 is a medium-severity server-side request forgery vulnerability in charmbracelet charm, published on 7 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in which attackers could forge HTTP requests to manipulate the `charm` data directory to access or delete anything on the server. This has been patched and is available in release [v0.12.1](https://github.com/charmbracelet/charm/releases/tag/v0.12.1). We recommend that all users running self-hosted `charm` instances update immediately. This vulnerability was found in-house and we haven't been notified of any potential exploiters. ### Additional notes * Encrypted user data uploaded to the Charm server is safe as Charm servers cannot decrypt user data. This includes filenames, paths, and all key-value data. * Users running the official Charm [Docker images](https://github.com/charmbracelet/charm/blob/main/docker.md) are at minimal risk because the exploit is limited to the containerized filesystem.

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

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

3 open source packages ship an affected version, including github.com/charmbracelet/charm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/charmbracelet/charm` | Go | From 0.9.0 | 0.12.1 |
| `github.com/charmbracelet/charm` | Go | From 0.9.0 | 0.12.1 |
| `github.com/charmbracelet/charm` | Go | From 0.9.0 | 0.12.1 |

Products: Charm Charm.

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

Upgrade github.com/charmbracelet/charm to 0.12.1 or later.

## Is CVE-2022-29180 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29180 is a medium-severity server-side request forgery vulnerability in charmbracelet charm, published on 7 May 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-29180 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/charmbracelet/charm (Go): affected from 0.9.0; fixed in 0.12.1
- github.com/charmbracelet/charm (Go): affected from 0.9.0; fixed in 0.12.1
- github.com/charmbracelet/charm (Go): affected from 0.9.0; fixed in 0.12.1

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

## Sources

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

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