Skip to content

← Public intelligence

crates.io package

tendermint-light-client-verifier

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.2crates.ioPublished

    tendermint-rs's Light Client Verifier allows malicious validators to spoof votes from other validators

    GHSA-6jrf-4jv4-r9mw

    Affected
    • crates.io tendermint-light-client-verifier < 0.40.3
    Fixed in
    0.40.3· Vendor fix available
    Issue
    Name: ISA-2025-003: Malicious validator can spoof votes from other validators Component: tendermint-rs Criticality: High (Catastrophic Impact; Rare Likelihood per ACMv1.2) Affected versions: <= v0.40.2 Affected users: Everyone Description tendermint-rs contains a critical vulnerability in its light client implementation due to insecure handling of corrupted validator sets. Because it doesn't check that the validator address is correctly derived from the validator's public key when counting votes, it is possible to spoof votes from other validators. The result is being able to construct the malicious block and cheat the light client. The light client will accept such a block, seemingly signed by 2/3+ majority. Patches The new tendermint-rs release v0.40.3 fixes this issue. Unreleased code in the main branch is patched as well. Workarounds There are no known workarounds for this issue. Timeline March 12, 2025, 13:41pm PST: Issue reported March 12, 2025, 03:00am PST: Core team completes…

    Recommended action: Upgrade to 0.40.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.4crates.ioPublished

    Tendermint light client verification not taking into account chain ID

    CVE-2022-23507 · GHSA-xqqc-c5gw-c5r5

    Affected
    • crates.io tendermint-light-client-verifier <= 0.27.0
    Fixed in
    0.28.0· Vendor fix available
    Issue
    Impact Anyone using the tendermint-light-client and related packages to perform light client verification (e.g. IBC-rs, Hermes). At present, the light client does not check that the chain IDs of the trusted and untrusted headers match, resulting in a possible attack vector where someone who finds a header from an untrusted chain that satisfies all other verification conditions (e.g. enough overlapping validator signatures) could fool a light client. The attack vector is currently theoretical, and no proof-of-concept exists yet to exploit it on live networks. Patches Users of the light client-related crates can currently upgrade to v0.28.0. Workarounds None References - Light Client specification

    Recommended action: Upgrade to 0.28.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →