-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Risk of Unhandled Failures #416
Comments
raymondfam marked the issue as insufficient quality report |
raymondfam marked the issue as duplicate of #25 |
weth and dcntEth are ERC20 tokens not to be mixed up with native coin using call(). |
alex-ppg marked the issue as not a duplicate |
The Warden has confused low-level calls (that always yield a |
alex-ppg marked the issue as unsatisfactory: |
Lines of code
https://github.com/decentxyz/decent-bridge/blob/7f90fd4489551b69c20d11eeecb17a3f564afb18/src/DecentEthRouter.sol#L285
https://github.com/decentxyz/decent-bridge/blob/7f90fd4489551b69c20d11eeecb17a3f564afb18/src/DecentEthRouter.sol#L302
Vulnerability details
In the
DecentEthRouter
contract, there are several instances where external calls are made to other contracts, such asweth.transfer
,weth.withdraw
,weth.deposit
, anddcntEth
contract calls. These calls are potentially unsafe as they don't handle the possibility of these calls failing or reverting:Impact
If external calls to WETH or other contracts fail, the current implementation does not handle these failures, which can lead to transaction reversion and inconsistent contract states.
Mitigation
To address these risks, handle the possibility of failures in external calls:
Assessed type
Error
The text was updated successfully, but these errors were encountered: