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
Describe The Bug
The self-transfer of any accounts lead to an unexpected coinsBurn of the asset handler located at /x/asset/keeper/keeper.go. Specifically, the Transfer() routine is designed to handle the KuTransfMsg message in order to transfer coins. However, the checks on the input message are not thorough. As a result, an accidental KuTransfMsg message which contains the same from and to account could lead to an unexpected coinsBurn behavior, causing asset losses to that user. In the following, we show the related code snippet.
Thanks for your submission.
We have tested the issue you mentioned and did reproduce it. This is a valid vulnerability. After evaluation, this vulnerability has been graded as P3.
Please pay attention to the announcement to get your rewards.
Thanks for your attention and contribution. Please keep trying and help us improve our chain.
Describe The Bug
The self-transfer of any accounts lead to an unexpected coinsBurn of the asset handler located at
/x/asset/keeper/keeper.go
. Specifically, theTransfer()
routine is designed to handle theKuTransfMsg
message in order to transfer coins. However, the checks on the input message are not thorough. As a result, an accidentalKuTransfMsg
message which contains the samefrom
andto
account could lead to an unexpectedcoinsBurn
behavior, causing asset losses to that user. In the following, we show the related code snippet.Code Snippets (Optional)
Input/Output
To Reproduce
Steps to reproduce the behavior:
Expected Behavior
Returns an error "
from
account cannot be equal toto
account".Screenshots
Desktop (please complete the following information):
Additional Context (Optional)
None
Contact Information
Email - [email protected]
The text was updated successfully, but these errors were encountered: