GHSA-q66h-m87m-j2q6: Bitcoinrb Bitcoinrb Vulnerable To Command Injection Vulnerability

LOW
Share
CWE-77
Published
Advisory Summary

GHSA-q66h-m87m-j2q6 is a LOW bitcoinrb vulnerable to command injection vulnerability (CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')) affecting Bitcoinrb libraries in the RubyGems ecosystem. The issue involves bitcoinrb vulnerable to command injection via rpc. Remediation is available by upgrading affected packages to version 1.12.0.

GHSA-q66h-m87m-j2q6 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-q66h-m87m-j2q6
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
Affected Product Bitcoinrb
Package Ecosystem RubyGems
Published Date
Last Updated

How to Fix GHSA-q66h-m87m-j2q6

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

bitcoinrb fixed: 1.12.0 
Upgrade bitcoinrb to 1.12.0
Verify Direct and Transitive Dependencies

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

inspect dependencies for bitcoinrb

How to Check if You Are Affected

To determine whether your application is affected by GHSA-q66h-m87m-j2q6, inspect your project dependencies for Bitcoinrb:

inspect dependencies for bitcoinrb

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

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'), where the product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. In Bitcoinrb, 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: Remote Code Execution Unsafe handling of request parameters in the RPC HTTP server results in command injection ### Details In lib/bitcoin/rpc/http_server.rb line 30-39, the JSON body of a POST request is parsed into `command` and `args` variables. These values are then passed to `send`, which is used to call an arbitrary class method. However, there is no validation that the provided `command` value is one of the expected RPC methods. This means that an attacker could supply a `command` value such as `system`, and then pass arbitrary system commands into the `args` parameter and achieve remote code execution. ### PoC 1. Start the RPC server 2. Send a request to the RPC server as so: ``` curl -X POST http://127.0.0.1:18443 -H 'Content-Type: application/json' \ -d '{"method":"eval","params":["File.write(\"/tmp/pwned\",\"owned\")"]}' ``` 3. Check the /tmp folder on the machine where the RPC server is being run. If a folder /pwned now exists, the vulnerability is confirmed. ### Impact This vulnerability would impact anyone running the RPC server. The impact is higher for those who are running it publicly exposed to the internet. ### Remediation **Mitigating Factors:** - The RPC server is part of the experimental SPV node feature, which is not documented and has very few users. - The SPV-related features may be removed in future releases. **Resolution:** - Added whitelist validation to allow only RPC methods defined in `RequestHandler`. - Fixed in version 1.12.0.

GHSA-q66h-m87m-j2q6 Affected Bitcoinrb Versions

1 component(s)
Fixed Versions:
1.12.0
Product / Package Ecosystem Affected Versions Fixed Version
bitcoinrb
gem/bitcoinrb
RubyGems
< 1.12.0
1.12.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/chaintope/bitcoinrb/security/advisories/GHSA-q66h-m87m-j2q6
Security Fix Commit FIX COMMIT
https://github.com/chaintope/bitcoinrb/commit/070327133a2a3e5a6d265b2d82f06f9414c01e74
Bitcoinrb Source Repository REPOSITORY
https://github.com/chaintope/bitcoinrb
Bitcoinrb Release RELEASE
https://github.com/chaintope/bitcoinrb/releases/tag/v1.12.0

Frequently Asked Questions

What is GHSA-q66h-m87m-j2q6?
GHSA-q66h-m87m-j2q6 is a security vulnerability in Bitcoinrb involving Bitcoinrb Vulnerable to Command injection via RPC under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection').
Which Bitcoinrb versions are affected?
Affected versions include releases prior to 1.12.0 across affected packages: bitcoinrb.
What version fixes GHSA-q66h-m87m-j2q6?
Upgrading to 1.12.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is bitcoinrb affected?
Yes, bitcoinrb is affected in releases prior to 1.12.0. Upgrade your dependency to 1.12.0 or later.
What CWE is associated with GHSA-q66h-m87m-j2q6?
GHSA-q66h-m87m-j2q6 is classified under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') (The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.).
How can I check RubyGems dependencies for GHSA-q66h-m87m-j2q6?
Run the dependency tree command: 'inspect dependencies for bitcoinrb'. 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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q66h-m87m-j2q6",
  "modified" : "2026-02-10T00:21:56Z",
  "published" : "2026-02-10T00:21:56Z",
  "aliases" : [ ],
  "summary" : "Bitcoinrb Vulnerable to Command injection via RPC ",
  "details" : "### Summary: Remote Code Execution\nUnsafe handling of request parameters in the RPC HTTP server results in command injection\n\n### Details\nIn lib/bitcoin/rpc/http_server.rb line 30-39, the JSON body of a POST request is parsed into `command` and `args` variables. These values are then passed to `send`, which is used to call an arbitrary class method. However, there is no validation that the provided `command` value is one of the expected RPC methods. \nThis means that an attacker could supply a `command` value such as `system`, and then pass arbitrary system commands into the `args` parameter and achieve remote code execution. \n\n### PoC\n1. Start the RPC server\n2. Send a request to the RPC server as so:\n ```\ncurl -X POST http://127.0.0.1:18443 -H 'Content-Type: application/json' \\\n    -d '{\"method\":\"eval\",\"params\":[\"File.write(\\\"/tmp/pwned\\\",\\\"owned\\\")\"]}'\n```\n3. Check the /tmp folder on the machine where the RPC server is being run. If a folder /pwned now exists, the vulnerability is confirmed.\n### Impact\nThis vulnerability would impact anyone running the RPC server. The impact is higher for those who are running it publicly exposed to the internet.\n\n### Remediation                                                \n                                                                                                                                                                                                                               \n  **Mitigating Factors:**                                                                                                                                                                                                      \n  - The RPC server is part of the experimental SPV node feature, which is not documented and has very few users.                                                                                                               \n  - The SPV-related features may be removed in future releases.                                                                                                                                                                \n                                                                                                                                                                                                                               \n  **Resolution:**                                                                                                                                                                                                              \n  - Added whitelist validation to allow only RPC methods defined in `RequestHandler`.                                                                                                                                          \n  - Fixed in version 1.12.0.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "RubyGems",
      "name" : "bitcoinrb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.12.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/chaintope/bitcoinrb/security/advisories/GHSA-q66h-m87m-j2q6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/chaintope/bitcoinrb/commit/070327133a2a3e5a6d265b2d82f06f9414c01e74"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/chaintope/bitcoinrb"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/chaintope/bitcoinrb/releases/tag/v1.12.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-77" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-10T00:21:56Z",
    "nvd_published_at" : null
  }
}