GHSA-8wcc-m6j2-qxvm ASA-2024-0012, ASA-2024-0013: CosmosSDK: Transaction decoding may result in a stack overflow or resource exhaustion
Attackers can cause network halts or node crashes via maliciously formed transactions with deep nesting or exponential resource consumption.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-8wcc-m6j2-qxvm?
GHSA-8wcc-m6j2-qxvm is a denial of service vulnerability in cosmossdk.io/x/tx, published on 16 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Summary
ASA-2024-0012
Name: ASA-2024-0012, Transaction decoding may result in a stack overflow Component: Cosmos SDK Criticality: High (Considerable Impact, and Possible Likelihood per ACMv1.2) Affected versions: cosmos-sdk versions <= v0.50.10, <= v0.47.14 Affected users: Chain Builders + Maintainers, Validators, node operators
ASA-2024-0013
Name: ASA-2024-0013: CosmosSDK: Transaction decoding may result in resource exhaustion
Component: Cosmos SDK
Criticality: High (Considerable Impact, and Possible Likelihood per ACMv1.2)
Affected versions: cosmos-sdk versions <= v0.50.10, <= v0.47.14
Affected users: Chain Builders + Maintainers, Validators, node operators
Impact
ASA-2024-0012
When decoding a maliciously formed packet with a deeply-nested structure, it may be possible for a stack overflow to occur and result in a network halt. This was addressed by adding a recursion limit while decoding the packet.
ASA-2024-0013
Nested messages in a transaction can consume exponential cpu and memory on UnpackAny calls. Themax_tx_bytes sets a limit for external TX but is not applied for internal messages emitted by wasm contracts or a malicious validator block. This may result in a node crashing due to resource exhaustion. This was addressed by adding additional validation to prevent this condition.
Patches
The issues above are resolved in Cosmos SDK versions v0.47.15 or v0.50.11. Please upgrade ASAP.
Timeline for ASA-2024-0012
- October 1, 2024, 12:29pm UTC: Issue reported to the Cosmos Bug Bounty program
- October 1, 2024, 2:47pm UTC: Issue triaged by Amulet on-call, and distributed to Core team
- December 9, 2024, 11:13am UTC: Core team completes patch for issue
- Dec 14, 2024,16:00 UTC: Pre-notification delivered
- Dec 16, 2024, 16:00 UTC: Patch made available
This issue was reported to the Cosmos Bug Bounty Program on HackerOne on October 1, 2024.
Timeline for ASA-2024-0013
- October 19, 2024, 8:12pm UTC: Issue reported to the Cosmos Bug Bounty program
- October 19, 2024, 8:28pm UTC: Issue triaged by Amulet on-call, and distributed to Core team
- December 11, 2024, 3:31pm UTC: Core team completes patch for issue
- Dec 14, 2024, 16:00 UTC: Pre-notification delivered
- Dec 16, 2024, 16:00 UTC: Patch made available
This issue was reported by LonelySloth to the Cosmos Bug Bounty Program on HackerOne on October 19, 2024.
If you believe you have found a bug in the Interchain Stack or would like to contribute to the program by reporting a bug, please see https://hackerone.com/cosmos.
If you have questions about Interchain security efforts, please reach out to our official communication channel at [email protected]. For more information about the Interchain Foundation’s engagement with Amulet, and to sign up for security notification emails, please see https://github.com/interchainio/security.
Which versions are affected by GHSA-8wcc-m6j2-qxvm?
8 open source packages ship an affected version, including cosmossdk.io/x/tx and github.com/cosmos/cosmos-sdk.
| Package | Affected | Fixed in |
|---|---|---|
cosmossdk.io/x/tx Go | All versions | 0.13.7 |
cosmossdk.io/x/tx Go | All versions | 0.13.7 |
cosmossdk.io/x/tx Go | All versions | 0.13.7 |
github.com/cosmos/cosmos-sdk Go | All versions | 0.47.15, 0.50.11 |
github.com/cosmos/cosmos-sdk Go | All versions | 0.47.15 |
github.com/cosmos/cosmos-sdk Go | All versions | 0.47.15 |
2 more packages
github.com/cosmos/cosmos-sdk Go | From 0.50.0-alpha.0 | 0.50.11 |
github.com/cosmos/cosmos-sdk Go | From 0.50.0-alpha.0 | 0.50.11 |
How do I fix GHSA-8wcc-m6j2-qxvm?
Upgrade cosmossdk.io/x/tx to 0.13.7 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is GHSA-8wcc-m6j2-qxvm being exploited?
There is no known exploitation of GHSA-8wcc-m6j2-qxvm in the wild and no public exploit code.
Sources
Also known as GO-2024-3339.