# CVE-2024-47180: Shields.io Remote Code Execution vulnerability in Dynamic JSON/TOML/YAML badges

> Attackers can execute arbitrary code on Shields.io instances by crafting malicious JSONPath expressions in dynamic badge requests.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2024
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-rxvx-x284-4445

## What is CVE-2024-47180?

CVE-2024-47180 is a high-severity code injection vulnerability in badges shields, published on 26 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Shields.io is a service for concise, consistent, and legible badges in SVG and raster format. Shields.io and users self-hosting their own instance of shields using version < `server-2024-09-25` are vulnerable to a remote execution vulnerability via the JSONPath library used by the Dynamic JSON/Toml/Yaml badges. This vulnerability would allow any user with access to make a request to a URL on the instance to the ability to execute code by crafting a malicious JSONPath expression. All users who self-host an instance are vulnerable. This problem was fixed in server-2024-09-25. Those who follow the tagged releases should update to `server-2024-09-25` or later. Those who follow the rolling tag on DockerHub, `docker pull shieldsio/shields:next` to update to the latest version. As a workaround, blocking access to the endpoints `/badge/dynamic/json`, `/badge/dynamic/toml`, and `/badge/dynamic/yaml` (e.g: via a firewall or reverse proxy in front of your instance) would prevent the exploitable endpoints from being accessed.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2024-47180?


## How do I fix CVE-2024-47180?

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

## Is CVE-2024-47180 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47180 and fix it if it is affected.

What it is: CVE-2024-47180 is a high-severity code injection vulnerability in badges shields, published on 26 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47180 in the wild and no public exploit code.

Affected product: badges shields. 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-2024-47180/ (Markdown: https://insights.sbomify.com/CVE-2024-47180/index.md)
```

## Sources

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

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