You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A vulnerability in the WASM integration and the authz module in the cosmos
-sdk has been detected, and was recently exploited to halt another chain
(JUNO). In the vulnerability, A smart contract abused non-deterministic
state in authz grants to save a different hash to all validators.
Juno Halt Root Cause Steps:
• An attacker is deployed a malicious contract on the Juno.
• A malicious contract is located on the Mint Scan
Problem Definition
• During the review of malicious contract, It has been observed that an
attacker’s contract is calling Authz Module MsgGrant and MsgRevoke.
• The smart contract leads to a non-determinism in Authz’s MsgGrant
where the grant expiration was suspected to default to the node’s
OS time if unset by the message sender.
• The reply() feature of CosmWasm allows calling a message and getting back its output events. With a couple of messages, a nondeterministic event ordering occurred in the Authz module, which
causes chain halt.
Proposal
Disable authz module on cosmwasm or wait for #12781 to be merged and update to that sdk
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary
A vulnerability in the WASM integration and the authz module in the cosmos
-sdk has been detected, and was recently exploited to halt another chain
(JUNO). In the vulnerability, A smart contract abused non-deterministic
state in authz grants to save a different hash to all validators.
Juno Halt Root Cause Steps:
• An attacker is deployed a malicious contract on the Juno.
• A malicious contract is located on the Mint Scan
Problem Definition
• During the review of malicious contract, It has been observed that an
attacker’s contract is calling Authz Module MsgGrant and MsgRevoke.
• The smart contract leads to a non-determinism in Authz’s MsgGrant
where the grant expiration was suspected to default to the node’s
OS time if unset by the message sender.
• The reply() feature of CosmWasm allows calling a message and getting back its output events. With a couple of messages, a nondeterministic event ordering occurred in the Authz module, which
causes chain halt.
Proposal
For Admin Use
The text was updated successfully, but these errors were encountered: