FKIE_CVE-2024-47883
Vulnerability from fkie_nvd - Published: 2024-10-24 21:15 - Updated: 2026-06-17 07:579.1 (Critical) - CVSS:3.1/
| Vendor | Product | Version | |
|---|---|---|---|
| openrefine | butterfly | * |
{
"affected": [
{
"affectedData": [
{
"product": "simile-butterfly",
"vendor": "OpenRefine",
"versions": [
{
"status": "affected",
"version": "\u003c 1.2.6"
}
]
}
],
"source": "security-advisories@github.com"
},
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:openrefine:similie_butterfly:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "similie_butterfly",
"vendor": "openrefine",
"versions": [
{
"lessThan": "1.2.6",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:openrefine:butterfly:*:*:*:*:*:*:*:*",
"matchCriteriaId": "11B5F36B-35D1-4FAA-AA42-E0E498458672",
"versionEndIncluding": "1.2.6",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s 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\u0027s 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\u0027s 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."
},
{
"lang": "es",
"value": "La bifurcaci\u00f3n OpenRefine del servidor MIT Simile Butterfly es un framework de trabajo de aplicaci\u00f3n web modular. El framework Butterfly utiliza la clase `java.net.URL` para hacer referencia a (lo que se espera que sean) archivos de recursos locales, como im\u00e1genes o plantillas. Esto funciona: \"abrir una conexi\u00f3n\" a estas URL abre el archivo local. Sin embargo, antes de la versi\u00f3n 1.2.6, si se proporciona directamente una URL `file:/` donde se espera una ruta relativa (nombre del recurso), esto tambi\u00e9n se acepta en algunas rutas de c\u00f3digo; la aplicaci\u00f3n luego obtiene el archivo, desde una m\u00e1quina remota si se indica, y lo usa como si fuera una parte confiable de la base de c\u00f3digo de la aplicaci\u00f3n. Esto conduce a m\u00faltiples debilidades y debilidades potenciales. Un atacante que tenga acceso de red a la aplicaci\u00f3n podr\u00eda usarlo para obtener acceso a archivos, ya sea en el sistema de archivos del servidor (path traversal) o compartidos por m\u00e1quinas cercanas (server-side request forgery con, por ejemplo, SMB). Un atacante que pueda dirigir o redirigir a un usuario a una URL manipulada que pertenezca a la aplicaci\u00f3n podr\u00eda provocar que se cargue c\u00f3digo JavaScript arbitrario controlado por el atacante en el navegador de la v\u00edctima (cross-site scripting). Si una aplicaci\u00f3n est\u00e1 escrita de tal manera que un atacante puede influir en el nombre del recurso utilizado para una plantilla, ese atacante podr\u00eda provocar que la aplicaci\u00f3n obtenga y ejecute una plantilla controlada por el atacante (ejecuci\u00f3n de c\u00f3digo remoto). La versi\u00f3n 1.2.6 contiene un parche."
}
],
"id": "CVE-2024-47883",
"lastModified": "2026-06-17T07:57:54.853",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.2,
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 9.1,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.2,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2024-47883",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-10-25T19:58:00.271372Z",
"version": "2.0.3"
}
}
]
},
"published": "2024-10-24T21:15:13.430",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/OpenRefine/simile-butterfly/commit/537f64bfa72746f8b21d4bda461fad843435319c"
},
{
"source": "security-advisories@github.com",
"tags": [
"Exploit",
"Vendor Advisory"
],
"url": "https://github.com/OpenRefine/simile-butterfly/security/advisories/GHSA-3p8v-w8mr-m3x8"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-36"
},
{
"lang": "en",
"value": "CWE-918"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-22"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.