Tadle

Tadle
DeFiFoundry
27,750 USDC
View results
Submission Details
Severity: high
Valid

Referral update function inadvertently allows creation of new referrals

Summary

The updateReferrerInfo function in the SystemConfig contract unintentionally allows the creation of new referrals in addition to updating existing ones. This can lead to unexpected behaviors and data integrity issues.

Vulnerability Details

The updateReferrerInfo function doesn't verify if the referral already exists before updating the information. If called with a non-existent referral address, it creates a new entry in the map.

function updateReferrerInfo(
address _referrer,
uint256 _referrerRate,
uint256 _authorityRate
) external {
// ...
ReferralInfo storage referralInfo = referralInfoMap[_referrer];
referralInfo.referrer = _referrer;
referralInfo.referrerRate = _referrerRate;
referralInfo.authorityRate = _authorityRate;
// ...
}

Impact

  1. Security: Malicious users could create unauthorized referral relationships.

  2. Data Integrity: May create unintended or invalid referral records.

  3. Business Logic: May interfere with the intended referral system logic, potentially affecting reward distribution.

Tools Used

Manual code analysis.

Recommendations

  1. Modify the updateReferrerInfo function to prevent creation of new referrals:

    • Add a check to ensure the referral exists before updating.

    • If the referral doesn't exist, the function should revert.

  2. Create a separate function for adding new referrals, if needed.

  3. Implement proper access controls for both update and creation functions.

  4. Update code documentation to clearly reflect the purpose and behavior of each function.

Updates

Lead Judging Commences

0xnevi Lead Judge 12 months ago
Submission Judgement Published
Validated
Assigned finding tags:

finding-SystemConfig-updateReferrerInfo-msgSender

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

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.