Incorrect setting of flow limit can lead to DoS #62
Labels
bug
Something isn't working
downgraded by judge
Judge downgraded the risk level of this issue
grade-b
primary issue
Highest quality submission among a set of duplicates
Q-19
QA (Quality Assurance)
Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
🤖_09_group
AI based duplicate group recommendation
sponsor confirmed
Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity")
sufficient quality report
This report is of sufficient quality
Lines of code
https://github.com/code-423n4/2024-08-axelar-network/blob/main/interchain-token-service/contracts/utils/FlowLimit.sol#L103-L105
Vulnerability details
Impact
Incorrect setting of flow limit can lead to DoS due to:
Proof of Concept
when an interchain token is deployed and initialSupply is greater than zero:
Minter address is assign FlowLimiter role otherwise interchainTokenService is assign flowlimit role.
Minter role can set any flowlimit value for a specific tokenManager:
However the flowLimit value is not checked , once type(uint256).max is used as the flowlimit value is can result in DOS.
This may go against the original intent of the setter.
test:
out:
Tools Used
Foundry
Recommended Mitigation Steps
limit the value of flowLimit
Assessed type
DoS
The text was updated successfully, but these errors were encountered: