{"answers":{"affected":"3 open source packages ship an affected version, including github.com/charmbracelet/charm. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-29180 in the wild and no public exploit code.","fix":"Upgrade github.com/charmbracelet/charm to 0.12.1 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2022-29180 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2022-29180 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/charmbracelet/charm (Go): affected from 0.9.0; fixed in 0.12.1\n- github.com/charmbracelet/charm (Go): affected from 0.9.0; fixed in 0.12.1\n- github.com/charmbracelet/charm (Go): affected from 0.9.0; fixed in 0.12.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-29180/ (Markdown: https://insights.sbomify.com/CVE-2022-29180/index.md)","id":"CVE-2022-29180","markdown":"https://insights.sbomify.com/CVE-2022-29180/index.md","name":"CVE-2022-29180","record":{"aliases":["GHSA-4wpp-w5r4-7v5v","GO-2022-0449"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Charm server software","requires_auth":"low_privilege","summary":"Attackers can forge HTTP requests to manipulate the Charm data directory, allowing access to or deletion of server files.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"charm","vendor":"charm"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Charm vulnerable to server-side request forgery (SSRF)","id":"CVE-2022-29180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"ssrf","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"Improper Handling of Unexpected Data Type in Nokogiri","id":"CVE-2022-29181"},"packages":[{"ecosystem":"Go","fixed":["0.12.1"],"introduced":["0.9.0"],"last_affected":[],"package":"github.com/charmbracelet/charm","purl":null,"source":"GHSA-4wpp-w5r4-7v5v"},{"ecosystem":"Go","fixed":["0.12.1"],"introduced":["0.9.0"],"last_affected":[],"package":"github.com/charmbracelet/charm","purl":"pkg:golang/github.com/charmbracelet/charm","source":"GHSA-4wpp-w5r4-7v5v"},{"ecosystem":"Go","fixed":["0.12.1"],"introduced":["0.9.0"],"last_affected":[],"package":"github.com/charmbracelet/charm","purl":"pkg:golang/github.com/charmbracelet/charm","source":"GO-2022-0449"}],"prev":{"headline":"Improper Privilege Management in Cilium","id":"CVE-2022-29179"},"products":["charm"],"published":"2022-05-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["charmbracelet"]},"summary":"Attackers can forge HTTP requests to manipulate the Charm data directory, allowing access to or deletion of server files.","url":"https://insights.sbomify.com/CVE-2022-29180/"}