Light client verification not taking into account chain ID
informalsystems tendermint-rs
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tendermint-light-client-verifier crates.io |
|
|
| tendermint-light-client crates.io |
|
|
| tendermint-light-client-js |
informalsystems tendermint-rs
| Product | Affected | Fixed in |
|---|---|---|
| tendermint-light-client-verifier crates.io |
|
|
| tendermint-light-client crates.io |
|
|
| tendermint-light-client-js |
|
|
Tendermint is a high-performance blockchain consensus engine for Byzantine fault tolerant applications. Versions prior to 0.28.0 contain a potential attack via Improper Verification of Cryptographic Signature, affecting anyone using the tendermint-light-client and related packages to perform light client verification (e.g. IBC-rs, Hermes). 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. This issue is patched in version 0.28.0. There are no workarounds.
From the CVE record · GitHub_M
Before 0.28.0, the Tendermint light client does not check that trusted and untrusted headers have matching chain IDs. An attacker who finds a header from another chain that meets the remaining verification conditions could fool a light client; this attack is theoretical, with no proof of concept on live networks. The input does not specify authentication or user-interaction requirements.
Check applications using tendermint-light-client-verifier, tendermint-light-client, or tendermint-light-client-js versions earlier than 0.28.0 for light client verification.