GHSA-mpcw-3j5p-p99x: Butterfly Remote Code Execution Vulnerability

MODERATE
CWE-185 CWE-95
Published
Advisory Summary

GHSA-mpcw-3j5p-p99x is a MODERATE remote code execution vulnerability (CWE-185: Incorrect Regular Expression) affecting Butterfly libraries in the Maven ecosystem. The issue involves butterfly's parsejson, getjson functions eval malicious input, leading to remote code execution (rce). Remediation is available by upgrading affected packages to version 1.2.6.

GHSA-mpcw-3j5p-p99x at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-mpcw-3j5p-p99x
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-185: Incorrect Regular Expression
Affected Product Butterfly
Package Ecosystem Maven
Published Date
Last Updated

How to Fix GHSA-mpcw-3j5p-p99x

To remediate this vulnerability, upgrade all affected Butterfly dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.openrefine.dependencies:butterfly fixed: 1.2.6
<dependency>
    <groupId>org.openrefine.dependencies</groupId>
    <artifactId>butterfly</artifactId>
    <version>1.2.6</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.openrefine.dependencies

How to Check if You Are Affected

To determine whether your Java application is affected by GHSA-mpcw-3j5p-p99x, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.openrefine.dependencies

Analyze the terminal output to locate any version of Butterfly in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.6), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.openrefine.dependencies command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-185: Incorrect Regular Expression, where the product specifies a regular expression in a way that causes data to be improperly matched or compared. In Butterfly, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary Usage of the `Butterfly.prototype.parseJSON` or `getJSON` functions on an attacker-controlled crafted input string allows the attacker to execute arbitrary JavaScript code on the server. Since Butterfly JavaScript code has access to Java classes, it can run arbitrary programs. ### Details The `parseJSON` function (edu/mit/simile/butterfly/Butterfly.js:64) works by calling `eval`, an approach that goes back to the original library by Crockford, before JSON was part of the ECMAScript language. It uses a regular expression to remove strings from the input, then checks that there are no unexpected characters in the non-string remainder. However, the regex is imperfect, as was [discovered earlier by Mike Samuel](https://dev.to/mikesamuel/2008-silently-securing-jsonparse-5cbb); specifically, the "cleaner" can be tricked into treating part of the input as a string that the "evaluator" does not, because of a difference in interpretation regarding the [the Unicode zero-width joiner character](https://unicode-explorer.com/c/200D). Representing that character with a visible symbol, a malicious input looks like: ```js "\�\", Packages.java.lang.Runtime.getRuntime().exec('gnome-calculator')) // " ``` This is understood... * by `JSON_cleaning_RE` as a single string, and because it is a string it can be collapsed to nothing, which is not problematic, so the original input proceeds to `eval`. * by the `eval` function, which ignores zero-width joiners entirely, as a string containing a single escaped backslash, followed by a comma, then a function call, closing parenthesis, and finally a line comment. The function call is evaluated, and a calculator is opened. Possible mitigations and additional defenses could include: * Replacing the JSON implementation with Rhino's built-in implementation. * Dropping all JSON-related and JSONP-related code entirely. * Restricting the access the JavaScript controller code has to the rest of the system by using `initSafeStandardObjects` instead of `initStandardObjects`, using `setClassShutter`, and so on. ### PoC Change OpenRefine `core` `controller.js` to add a call to the vulnerable `getJSON` function: ```diff diff --git a/main/webapp/modules/core/MOD-INF/controller.js b/main/webapp/modules/core/MOD-INF/controller.js index 4ceba0676..1ce0936d2 100644 --- a/main/webapp/modules/core/MOD-INF/controller.js +++ b/main/webapp/modules/core/MOD-INF/controller.js @@ -631,0 +632,5 @@ function process(path, request, response) { + if (path == "getjsontest") { + butterfly.getJSON(request); + return true; + } + ``` Then, restart OpenRefine and submit the malicious request. For example, the following `bash` command (with $' quoting) should do it: ``` curl -H 'Content-Type: application/json;charset=utf-8' --data $'"\\\u200d\\", Packages.java.lang.Runtime.getRuntime().exec(\'gnome-calculator\')) // "' http://localhost:3333/getjsontest ``` ### Impact Any JavaScript controller that calls one of these functions is vulnerable to remote code execution. OpenRefine itself seems unaffected; both OpenRefine and jQuery have their own functions also called parseJSON and getJSON, but those are unrelated.

GHSA-mpcw-3j5p-p99x Affected Butterfly Versions

1 component(s)
Fixed Versions:
1.2.6
Product / Package Ecosystem Affected Versions Fixed Version
org.openrefine.dependencies:butterfly
Maven
< 1.2.6
1.2.6

References

Frequently Asked Questions

What is GHSA-mpcw-3j5p-p99x?
GHSA-mpcw-3j5p-p99x is a security vulnerability in Butterfly involving Butterfly's parseJSON, getJSON functions eval malicious input, leading to remote code execution (RCE) under CWE-185: Incorrect Regular Expression.
Which Butterfly versions are affected?
Affected versions include releases prior to 1.2.6 across affected packages: org.openrefine.dependencies:butterfly.
What version fixes GHSA-mpcw-3j5p-p99x?
Upgrading to 1.2.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is butterfly affected?
Yes, org.openrefine.dependencies:butterfly is affected in releases prior to 1.2.6. Upgrade your dependency to 1.2.6 or later.
What CWE is associated with GHSA-mpcw-3j5p-p99x?
GHSA-mpcw-3j5p-p99x is classified under CWE-185: Incorrect Regular Expression (The product specifies a regular expression in a way that causes data to be improperly matched or compared.).
How can I check Maven dependencies for GHSA-mpcw-3j5p-p99x?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.openrefine.dependencies'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mpcw-3j5p-p99x",
  "modified" : "2024-10-24T18:27:50Z",
  "published" : "2024-10-24T18:27:50Z",
  "aliases" : [ ],
  "summary" : "Butterfly's parseJSON, getJSON functions eval malicious input, leading to remote code execution (RCE)",
  "details" : "### Summary\n\nUsage of the `Butterfly.prototype.parseJSON` or `getJSON` functions on an attacker-controlled crafted input string allows the attacker to execute arbitrary JavaScript code on the server.\n\nSince Butterfly JavaScript code has access to Java classes, it can run arbitrary programs.\n\n### Details\n\nThe `parseJSON` function (edu/mit/simile/butterfly/Butterfly.js:64) works by calling `eval`, an approach that goes back to the original library by Crockford, before JSON was part of the ECMAScript language. It uses a regular expression to remove strings from the input, then checks that there are no unexpected characters in the non-string remainder.\n\nHowever, the regex is imperfect, as was [discovered earlier by Mike Samuel](https://dev.to/mikesamuel/2008-silently-securing-jsonparse-5cbb); specifically, the \"cleaner\" can be tricked into treating part of the input as a string that the \"evaluator\" does not, because of a difference in interpretation regarding the [the Unicode zero-width joiner character](https://unicode-explorer.com/c/200D). Representing that character with a visible symbol, a malicious input looks like:\n\n```js\n\"\\�\\\", Packages.java.lang.Runtime.getRuntime().exec('gnome-calculator')) // \"\n```\n\nThis is understood...\n\n* by `JSON_cleaning_RE` as a single string, and because it is a string it can be collapsed to nothing, which is not problematic, so the original input proceeds to `eval`.\n* by the `eval` function, which ignores zero-width joiners entirely, as a string containing a single escaped backslash, followed by a comma, then a function call, closing parenthesis, and finally a line comment.\n \nThe function call is evaluated, and a calculator is opened.\n\nPossible mitigations and additional defenses could include:\n\n* Replacing the JSON implementation with Rhino's built-in implementation.\n* Dropping all JSON-related and JSONP-related code entirely.\n* Restricting the access the JavaScript controller code has to the rest of the system by using `initSafeStandardObjects` instead of `initStandardObjects`, using `setClassShutter`, and so on.\n\n### PoC\n\nChange OpenRefine `core` `controller.js` to add a call to the vulnerable `getJSON` function:\n\n```diff\ndiff --git a/main/webapp/modules/core/MOD-INF/controller.js b/main/webapp/modules/core/MOD-INF/controller.js\nindex 4ceba0676..1ce0936d2 100644\n--- a/main/webapp/modules/core/MOD-INF/controller.js\n+++ b/main/webapp/modules/core/MOD-INF/controller.js\n@@ -631,0 +632,5 @@ function process(path, request, response) {\n+    if (path == \"getjsontest\") {\n+      butterfly.getJSON(request);\n+      return true;\n+    }\n+\n```\n\nThen, restart OpenRefine and submit the malicious request. For example, the following `bash` command (with $' quoting) should do it:\n\n```\ncurl -H 'Content-Type: application/json;charset=utf-8' --data $'\"\\\\\\u200d\\\\\", Packages.java.lang.Runtime.getRuntime().exec(\\'gnome-calculator\\')) // \"' http://localhost:3333/getjsontest\n```\n\n### Impact\n\nAny JavaScript controller that calls one of these functions is vulnerable to remote code execution.\n\nOpenRefine itself seems unaffected; both OpenRefine and jQuery have their own functions also called parseJSON and getJSON, but those are unrelated.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.openrefine.dependencies:butterfly"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.2.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/OpenRefine/simile-butterfly/security/advisories/GHSA-mpcw-3j5p-p99x"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/OpenRefine/simile-butterfly/commit/2ad1fa4cd8afe3c920c8e6e04fe7a7df5cf8294e"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/OpenRefine/simile-butterfly"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-185", "CWE-95" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-10-24T18:27:50Z",
    "nvd_published_at" : null
  }
}