Tendermint Light Client
Approved changes feed: RSS · Atom
cpe:2.3:a:tendermint-light-client_project:tendermint-light-client:*:*:*:*:rust:*:*:*part: a version: * update: *
| Vendor | Tendermint Light Client Project (2e563689-5e64-5e87-9513-005cdeb67060) |
|---|---|
| Product | Tendermint Light Client (f769cb0d-07c0-5d74-8209-a8d2d80c3bdb) |
| Edition | * |
| Language | * |
| Software edition | rust |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/informalsystems/tendermint-rs |
purl2cpe | 2026-06-01 10:15:32.585892 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-23507 |
vulnerable | 2026-06-08 05:40:57.664185 |
Light client verification not taking into account chain ID
MEDIUM (5.4)
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.
Published: 2022-12-15T00:01:04.540Z
Updated: 2025-04-18T15:59:54.978Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.