RUSTSEC-2026-0497 (GHSA-84XQ-3662-PVX5)

Vulnerability from osv_rustsec – Published: 2026-11-11 12:00 – Updated: 2026-11-12 07:53 – Source website
VLAI
Summary
Transaction::from_json holds an input txid that is not 64 hex digits and writes the input as spending the zero txid
Details

Transaction::from_json, for a document with no hex member, held each input's txid member as given. An input txid that is not 64 hex digits ("zz", "", 63 or 65 digits, characters that are not hex digits) answered Ok: source_txid and to_json gave the text back, while to_binary wrote the input as spending the txid of 32 zero bytes and id() hashed those bytes. Documents naming different texts were one transaction, spending an outpoint none of them named.

An application that reads a peer's transaction document with from_json and relies both on the text of its inputs and on its bytes or id() is affected; one that reads only documents it produced is not.

0.8.6 refuses such a txid (Invalid txid of input N: expected 64 hex digits). Where upgrading is not possible, require each input's txid to be 64 ASCII hex digits before calling from_json.


{
  "affected": [
    {
      "database_specific": {
        "categories": [],
        "cvss": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
        "informational": null
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [
            "bsv_rs::transaction::Transaction::from_json"
          ],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "bsv-rs",
        "purl": "pkg:cargo/bsv-rs"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-0"
            },
            {
              "fixed": "0.8.6"
            },
            {
              "introduced": "0.9.0-beta.1"
            },
            {
              "fixed": "0.9.0-beta.7.0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [
    "GHSA-84xq-3662-pvx5"
  ],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "`Transaction::from_json`, for a document with no `hex` member, held each\ninput\u0027s `txid` member as given. An input `txid` that is not 64 hex digits\n(`\"zz\"`, `\"\"`, 63 or 65 digits, characters that are not hex digits) answered\n`Ok`: `source_txid` and `to_json` gave the text back, while `to_binary` wrote\nthe input as spending the txid of 32 zero bytes and `id()` hashed those bytes.\nDocuments naming different texts were one transaction, spending an outpoint\nnone of them named.\n\nAn application that reads a peer\u0027s transaction document with `from_json` and\nrelies both on the text of its inputs and on its bytes or `id()` is affected;\none that reads only documents it produced is not.\n\n0.8.6 refuses such a txid (`Invalid txid of input N: expected 64 hex digits`).\nWhere upgrading is not possible, require each input\u0027s `txid` to be 64 ASCII hex\ndigits before calling `from_json`.",
  "id": "RUSTSEC-2026-0497",
  "modified": "2026-11-12T07:53:20Z",
  "published": "2026-11-11T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/bsv-rs"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2026-0497.html"
    },
    {
      "type": "WEB",
      "url": "https://github.com/Calhooon/bsv-rs/blob/v0.8.6/CHANGELOG.md"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/Calhooon/bsv-rs/issues/845"
    },
    {
      "type": "WEB",
      "url": "https://github.com/Calhooon/bsv-rs/pull/856"
    }
  ],
  "related": [],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Transaction::from_json holds an input txid that is not 64 hex digits and writes the input as spending the zero txid"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.

Loading…

Loading…

Loading…

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.


Loading…