GHSA-7mm3-vfg8-7rg6: Github.com/babylonlabs io/babylon Babylon Finality Provider `MsgCommitPubRandList` Replay Vulnerability

HIGH
CWE-290
Published
Advisory Summary

GHSA-7mm3-vfg8-7rg6 is a HIGH babylon finality provider `msgcommitpubrandlist` replay vulnerability (CWE-290: Authentication Bypass by Spoofing) affecting Github.com/babylonlabs io/babylon libraries in the Go ecosystem. The issue involves babylon finality provider `msgcommitpubrandlist` replay attack. Remediation is available by upgrading affected packages to version 1.1.0.

GHSA-7mm3-vfg8-7rg6 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-7mm3-vfg8-7rg6
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-290: Authentication Bypass by Spoofing
Affected Product Github.com/babylonlabs io/babylon
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-7mm3-vfg8-7rg6

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

github.com/babylonlabs-io/babylon fixed: 1.1.0
Upgrade github.com/babylonlabs-io/babylon to 1.1.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 github.com/babylonlabs-io/babylon

How to Check if You Are Affected

To determine whether your application is affected by GHSA-7mm3-vfg8-7rg6, inspect your project dependencies for Github.com/babylonlabs io/babylon:

inspect dependencies for github.com/babylonlabs-io/babylon

Analyze the terminal output to locate any version of Github.com/babylonlabs io/babylon in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.1.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-290: Authentication Bypass by Spoofing, where this attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks. In Github.com/babylonlabs io/babylon, 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 A high vulnerability exists in the Babylon protocol's x/finality module due to a lack of domain separation in signed messages, combined with insufficient validation in the MsgCommitPubRandList handler. Specifically, the handler does not enforce that the submitted Commitment field is 32 bytes long. This allows an attacker to replay a signature originally generated for a different message (e.g., a Proof-of-Possession in MsgCreateFinalityProvider) as a MsgCommitPubRandList. By crafting the message parameters, an attacker can use the typically 20-byte address bytes (from the PoP context) to form the StartHeight, NumPubRand, and a shorter-than-expected Commitment (e.g., 4 bytes). The replayed signature will pass verification for this crafted message, leading to the injection of an invalid PubRand commitment. ### Impact Successful exploitation of this vulnerability, specifically via the PoP signature replay, allows an attacker to store an invalid PubRand commitment (with a non-standard length, e.g., 4 bytes) for a targeted Finality Provider (FP). Despite the commitment itself being malformed, it's the associated StartHeight and NumPubRand (derived from the replayed address bytes and typically very large) that cause severe consequences ### Future recommendations To minimize future risk of such attacks, all finality providers should: 1. Never re-use your finality provider EOTS across the networks (e.g., the testnet) or for any other purpose. 2. Never use EOTS keys to sign any other data than relevant to in-protocol messages. Ideally EOTS key should only be used to: - Sign initial proof of possession message - Sign periodic randomness commits - Sign finality votes with every block ### Finder Vulnerability discovered by: - Marco Hextor - https://x.com/marcohextor - @marcohextor

GHSA-7mm3-vfg8-7rg6 Affected Github.com/babylonlabs io/babylon Versions

1 component(s)
Fixed Versions:
1.1.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/babylonlabs-io/babylon
Go
< 1.1.0
1.1.0

References

Frequently Asked Questions

What is GHSA-7mm3-vfg8-7rg6?
GHSA-7mm3-vfg8-7rg6 is a security vulnerability in Github.com/babylonlabs io/babylon involving Babylon Finality Provider `MsgCommitPubRandList` replay attack under CWE-290: Authentication Bypass by Spoofing.
Which Github.com/babylonlabs io/babylon versions are affected?
Affected versions include releases prior to 1.1.0 across affected packages: github.com/babylonlabs-io/babylon.
What version fixes GHSA-7mm3-vfg8-7rg6?
Upgrading to 1.1.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/babylonlabs-io/babylon affected?
Yes, github.com/babylonlabs-io/babylon is affected in releases prior to 1.1.0. Upgrade your dependency to 1.1.0 or later.
What CWE is associated with GHSA-7mm3-vfg8-7rg6?
GHSA-7mm3-vfg8-7rg6 is classified under CWE-290: Authentication Bypass by Spoofing (This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.).
How can I check Go dependencies for GHSA-7mm3-vfg8-7rg6?
Run the dependency tree command: 'inspect dependencies for github.com/babylonlabs-io/babylon'. 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-7mm3-vfg8-7rg6",
  "modified" : "2025-07-31T16:43:43Z",
  "published" : "2025-05-15T14:05:32Z",
  "aliases" : [ ],
  "summary" : "Babylon Finality Provider `MsgCommitPubRandList` replay attack",
  "details" : "### Summary\n\nA high vulnerability exists in the Babylon protocol's x/finality module due to a lack of domain separation in signed messages, combined with insufficient validation in the MsgCommitPubRandList handler. Specifically, the handler does not enforce that the submitted Commitment field is 32 bytes long. This allows an attacker to replay a signature originally generated for a different message (e.g., a Proof-of-Possession in MsgCreateFinalityProvider) as a MsgCommitPubRandList. By crafting the message parameters, an attacker can use the typically 20-byte address bytes (from the PoP context) to form the StartHeight, NumPubRand, and a shorter-than-expected Commitment (e.g., 4 bytes). The replayed signature will pass verification for this crafted message, leading to the injection of an invalid PubRand commitment.\n\n### Impact\n\nSuccessful exploitation of this vulnerability, specifically via the PoP signature replay, allows an attacker to store an invalid PubRand commitment (with a non-standard length, e.g., 4 bytes) for a targeted Finality Provider (FP). Despite the commitment itself being malformed, it's the associated StartHeight and NumPubRand (derived from the replayed address bytes and typically very large) that cause severe consequences\n\n### Future recommendations\n\nTo minimize future risk of such attacks, all finality providers should:\n1.  Never re-use your finality provider EOTS across the networks (e.g., the testnet) or for any other purpose. \n2. Never use EOTS keys to sign any other data than relevant to in-protocol messages. Ideally EOTS key should only be used to:\n    - Sign initial proof of possession message\n    - Sign periodic randomness commits\n    - Sign finality votes with every block\n\n### Finder\nVulnerability discovered by:\n- Marco Hextor\n- https://x.com/marcohextor\n- @marcohextor",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/babylonlabs-io/babylon"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.1.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/babylonlabs-io/babylon/security/advisories/GHSA-7mm3-vfg8-7rg6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/babylonlabs-io/babylon/commit/cb5d0ecae5cebc116d09296baaed25f715f904df"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/babylonlabs-io/babylon"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2025-3686"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-290" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-05-15T14:05:32Z",
    "nvd_published_at" : null
  }
}