Summary
The likeUser
function in the LikeRegistry contract has a critical flaw where it accepts ETH payments from users but fails to update their balances in the userBalances
mapping.
Vulnerability Details
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 send ETH but their balances aren't recorded
-
When matches occur, the matchRewards
function sees 0 balances
-
Users lose their invested ETH as it's stuck in the contract
-
The entire matching reward system breaks down
Recommendations
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");
+ userBalances[msg.sender] += msg.value;
likes[msg.sender][liked] = true;
emit Liked(msg.sender, liked);
emit UserBalanceUpdated(msg.sender, userBalances[msg.sender]);
if (likes[liked][msg.sender]) {
_processMatch(msg.sender, liked);
}
}