GHSA-3W94-VQ2X-V5WR

Vulnerability from github – Published: 2025-07-02 15:12 – Updated: 2025-07-02 18:59
VLAI?
Summary
ethereum does not check transaction malleability for EIP-2930, EIP-1559 and EIP-7702 transactions
Details

Impact

Prior to ethereum crate v0.18.0, signature malleability (according to EIP-2) was only checked for "legacy" transactions, but not for EIP-2930, EIP-1559 and EIP-7702 transactions.

This is a specification deviation and therefore a high severity advisory if the ethereum crate is used for Ethereum mainnet. Note that signature malleability itself is not a security issue, and therefore if the ethereum crate is used on a single-implementation blockchain, it's a low/informational severity advisory.

Patches

The issue is fixed in ethereum v0.18.0

Workarounds

You can also manually check transaction malleability outside of the crate. But it's recommended to simply upgrade the version.

References

See PR: https://github.com/rust-ethereum/ethereum/pull/67

Severity ?
6.9 (Medium)
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "crates.io",
        "name": "ethereum"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.18.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-53359"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-754"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-07-02T15:12:18Z",
    "nvd_published_at": "2025-07-02T16:15:29Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nPrior to `ethereum` crate v0.18.0, signature malleability (according to EIP-2) was only checked for \"legacy\" transactions, but not for EIP-2930, EIP-1559 and EIP-7702 transactions.\n\nThis is a specification deviation and therefore a high severity advisory if the `ethereum` crate is used for Ethereum mainnet. Note that signature malleability itself is not a security issue, and therefore if the `ethereum` crate is used on a single-implementation blockchain, it\u0027s a low/informational severity advisory.\n\n### Patches\n\nThe issue is fixed in `ethereum` v0.18.0\n\n### Workarounds\n\nYou can also manually check transaction malleability outside of the crate. But it\u0027s recommended to simply upgrade the version.\n\n### References\n\nSee PR: https://github.com/rust-ethereum/ethereum/pull/67",
  "id": "GHSA-3w94-vq2x-v5wr",
  "modified": "2025-07-02T18:59:52Z",
  "published": "2025-07-02T15:12:18Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/rust-ethereum/ethereum/security/advisories/GHSA-3w94-vq2x-v5wr"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-53359"
    },
    {
      "type": "WEB",
      "url": "https://github.com/rust-ethereum/ethereum/pull/67"
    },
    {
      "type": "WEB",
      "url": "https://github.com/rust-ethereum/ethereum/commit/2dd9d1d5d0936ec7350093ff3a5a7169a349db77"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/rust-ethereum/ethereum"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "ethereum does not check transaction malleability for EIP-2930, EIP-1559 and EIP-7702 transactions"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

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.



Detection rules are retrieved from Rulezet.