Open zlsecure3 opened 1 year ago
submission_id:1761909491
review_type:GRADING
result: TBD-yes,no
rating: TBD-123
comment: TBD-Rejected,Accepted by Secure3.
severity: TBD-Critical,Medium,Low,Informational
category:
description:
submission_id:1761909491
review_type:CLIENT_FEEDBACK
result: TBD-yes,no
severity: TBD-Critical,Medium,Low,Informational
comment:
submission_id:1761909491
review_type:CLIENT_FEEDBACK_DECISION
result: TBD-yes,no,yes-honored,no-honored
severity: TBD-Critical,Medium,Low,Informational
comment:
subject
it's possible that two different tokens assigned the same assetId in
ReserveStorage::setReserveConfig
functiondescription
If two different tokens are assigned the same
assetId
(e.g, btc and doge are assigned the sameassetId
), serious result may occur(e.g, one can deposit doge as btc).But current implementation doesn't check against this situation, it's quite trivial to add it back.
change:
to
The above also ensures that
assetId
can't be0
, which current implementation misses checking in theelse
branch.recommendation
Apply the above fix.
locations
severity
Medium
damage
exploitability
category
Logical
system_generated: auditor:alansh submission_id:1761909491