# CVE-2024-47883: Butterfly has path/URL confusion in resource handling leading to multiple weaknesses

> Attackers can exploit URL confusion to read local files, perform SSRF, or execute remote code via malicious templates in Butterfly-based applications.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Oct 2024
- **Updated:** 25 Oct 2024
- **Also known as:** DEBIAN-CVE-2024-47883, GHSA-3p8v-w8mr-m3x8, UBUNTU-CVE-2024-47883

## What is CVE-2024-47883?

CVE-2024-47883 is a critical path traversal vulnerability in OpenRefine simile-butterfly, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The OpenRefine fork of the MIT Simile Butterfly server is a modular web application framework. The Butterfly framework uses the `java.net.URL` class to refer to (what are expected to be) local resource files, like images or templates. This works: "opening a connection" to these URLs opens the local file. However, prior to version 1.2.6, if a `file:/` URL is directly given where a relative path (resource name) is expected, this is also accepted in some code paths; the app then fetches the file, from a remote machine if indicated, and uses it as if it was a trusted part of the app's codebase. This leads to multiple weaknesses and potential weaknesses. An attacker that has network access to the application could use it to gain access to files, either on the the server's filesystem (path traversal) or shared by nearby machines (server-side request forgery with e.g. SMB). An attacker that can lead or redirect a user to a crafted URL belonging to the app could cause arbitrary attacker-controlled JavaScript to be loaded in the victim's browser (cross-site scripting). If an app is written in such a way that an attacker can influence the resource name used for a template, that attacker could cause the app to fetch and execute an attacker-controlled template (remote code execution). Version 1.2.6 contains a patch.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-918 (Server-Side Request Forgery), CWE-36 (Absolute Path Traversal)

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

2 open source packages ship an affected version, including org.openrefine.dependencies:butterfly. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.openrefine.dependencies:butterfly` | Maven | All versions | 1.2.6 |
| `org.openrefine.dependencies:butterfly` | Maven | All versions | 1.2.6 |

Products: Openrefine Butterfly.

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

Upgrade org.openrefine.dependencies:butterfly to 1.2.6 or later.

## Is CVE-2024-47883 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47883 is a critical path traversal vulnerability in OpenRefine simile-butterfly, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47883 exists.

Affected packages and fixed versions:
- org.openrefine.dependencies:butterfly (Maven): affected all versions; fixed in 1.2.6
- org.openrefine.dependencies:butterfly (Maven): affected all versions; fixed in 1.2.6

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

## Sources

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

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