The updateReferrerInfo() function allowing any user to call it and set the referral relationship to referer => referralInfo, resulting in the referrer of an account is the account itself. This vulnerability enables anyone to change another user's referrer, leading to a corrupted referral system.
The updateReferrerInfo() function allows updating a user's referral information. The referral data is stored in the referralInfoMap(user => referralInfo) mapping, which tracks referral information for each user.
The function incorrectly uses _referrer as the key in the referralInfoMap mapping (L69), which should instead represent the user account whose referral information is being updated. This results in the mapping storing referrer => referralInfo, meaning that the referrer is mapped to itself:
Allowing unauthorized users to alter referral relationships, leading to a corrupted referral system.
vscode
Valid high severity. There are two impacts here due to the wrong setting of the `refferalInfoMap` mapping. 1. Wrong refferal info is always set, so the refferal will always be delegated to the refferer address instead of the caller 2. Anybody can arbitrarily change the referrer and referrer rate of any user, resulting in gaming of the refferal system I prefer #1500 description the most, be cause it seems to be the only issue although without a poc to fully describe all of the possible impacts
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.