Vulnerability Details
The LikeRegistry::likeUser
function requires users to send at least 1 ETH to like another user. However, the function does not refund any excess ETH sent beyond the required 1 ETH. This leads to a logical flaw, as users expect only 1 ETH to be deducted while any extra amount should be refunded.
Code Snippet:
function likeUser(
address liked
) external payable {
require(msg.value >= 1 ether, "Must send at least 1 ETH");
require(!likes[msg.sender][liked], "Already liked");
require(msg.sender != liked, "Cannot like yourself");
require(profileNFT.profileToToken(msg.sender) != 0, "Must have a profile NFT");
require(profileNFT.profileToToken(liked) != 0, "Liked user must have a profile NFT");
likes[msg.sender][liked] = true;
emit Liked(msg.sender, liked);
if (likes[liked][msg.sender]) {
matches[msg.sender].push(liked);
matches[liked].push(msg.sender);
emit Matched(msg.sender, liked);
matchRewards(liked, msg.sender);
}
}
Impact
Users who send more than 1 ETH will lose the extra funds, leading to frustration and potential loss of trust.
Recommendations
Implement an Explicit Refund Mechanism
Modify the function to return excess ETH:
function likeUser(address liked) external payable {
require(msg.value >= 1 ether, "Must send at least 1 ETH");
require(!likes[msg.sender][liked], "Already liked");
require(msg.sender != liked, "Cannot like yourself");
require(profileNFT.profileToToken(msg.sender) != 0, "Must have a profile NFT");
require(profileNFT.profileToToken(liked) != 0, "Liked user must have a profile NFT");
uint256 excessAmount = msg.value - 1 ether;
if (excessAmount > 0) {
payable(msg.sender).transfer(excessAmount);
}
likes[msg.sender][liked] = true;
emit Liked(msg.sender, liked);
if (likes[liked][msg.sender]) {
matches[msg.sender].push(liked);
matches[liked].push(msg.sender);
emit Matched(msg.sender, liked);
matchRewards(liked, msg.sender);
}
}