What is CVE-2022-29180?

CVE-2022-29180 is a critical-severity server-side request forgery (SSRF) vulnerability in github.com/charmbracelet/charm (go), affecting versions >= 0.9.0, < 0.12.1. It is fixed in 0.12.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.

How severe is CVE-2022-29180?

CVE-2022-29180 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/charmbracelet/charm are affected by CVE-2022-29180?

github.com/charmbracelet/charm (go) versions >= 0.9.0, < 0.12.1 is affected.

Is there a fix for CVE-2022-29180?

Yes. CVE-2022-29180 is fixed in 0.12.1. Upgrade to this version or later.

Is CVE-2022-29180 exploitable, and should I be worried?

Whether CVE-2022-29180 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2022-29180 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2022-29180 in github.com/charmbracelet/charm

Q: How severe is CVE-2022-29180?

CVE-2022-29180 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/charmbracelet/charm are affected by CVE-2022-29180?

github.com/charmbracelet/charm (go) versions >= 0.9.0, < 0.12.1 is affected.

Q: Is there a fix for CVE-2022-29180?

Yes. CVE-2022-29180 is fixed in 0.12.1. Upgrade to this version or later.

Q: Is CVE-2022-29180 exploitable, and should I be worried?

Whether CVE-2022-29180 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2022-29180 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2022-29180?

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

Summary

Server-Side Request Forgery in charm

We've discovered 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 in https://github.com/charmbracelet/charm/commit/3c90668f955c7ce5ef721e4fc9faee7053232fd3 and is available in release 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 are at minimal risk because the exploit is limited to the containerized filesystem.

For more information

If you have any questions or comments about this advisory:

Open a discussion
Email us at [email protected]
Chat with us on Slack

Charm热爱开源 • Charm loves open source

Impact

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2022-29180 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.12.1); upgrading removes the vulnerable code path.

Affected versions

github.com/charmbracelet/charm (>= 0.9.0, < 0.12.1)

Security releases

github.com/charmbracelet/charm → 0.12.1 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/charmbracelet/charm to 0.12.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-29180? CVE-2022-29180 is a critical-severity server-side request forgery (SSRF) vulnerability in github.com/charmbracelet/charm (go), affecting versions >= 0.9.0, < 0.12.1. It is fixed in 0.12.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
How severe is CVE-2022-29180? CVE-2022-29180 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/charmbracelet/charm are affected by CVE-2022-29180? github.com/charmbracelet/charm (go) versions >= 0.9.0, < 0.12.1 is affected.
Is there a fix for CVE-2022-29180? Yes. CVE-2022-29180 is fixed in 0.12.1. Upgrade to this version or later.
Is CVE-2022-29180 exploitable, and should I be worried? Whether CVE-2022-29180 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2022-29180 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2022-29180? Upgrade github.com/charmbracelet/charm to 0.12.1 or later.