CVE-2023-42806
Iohk Hydra vulnerability
Hydra is the layer-two scalability solution for Cardano. Prior to version 0.13.0, not signing and verifying `$\mathsf{cid}$` allows an attacker (which must be a participant of this head) to use a snapshot from an old head instance with the same participants to close the head or contest the state with it. This can lead to an incorrect distribution of value (= value extraction attack; hard, but possible) or prevent the head to finalize because the value available is not consistent with the closed utxo state (= denial of service; easy). A patch is planned for version 0.13.0. As a workaround, rotate keys between heads so not to re-use keys and not result in the same multi-signature participants.
Affected products
Hydra. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Iohk Hydra runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/input-output-hk/hydra/security/advisories/GHSA-gr36-mc6v-72qq · Vendor Advisory
- github.com/input-output-hk/hydra/blob/ec6c7a2ab651462228475d0b34264e9a182c22bb/hydra-node/
- github.com/input-output-hk/hydra/blob/ec6c7a2ab651462228475d0b34264e9a182c22bb/hydra-node/
- github.com/input-output-hk/hydra/blob/ec6c7a2ab651462228475d0b34264e9a182c22bb/hydra-plutu
- nvd.nist.gov/vuln/detail/CVE-2023-42806
- cve.org/CVERecord?id=CVE-2023-42806
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.