Purchase() function is not updatinglistings mapping, allowing the previous creator to control the nft and also loss of funds for the buyer.
A purchase can be made via purchase() method in buyerAgent.sol, which makes a call to same named function in swan contract. Let's look at the purchase() function in swan contract:
the nft is transfered to listing.buyer, however the listings mapping is not updated to reflect that the new buyer is the asset's current owner. This means that after purchase, the seller field in listings[_asset] still references the original seller, not the new owner. There are two potential impacts in this case:)
The asset can be controlled by the previous creator(seller). For example the previous creator can relist the asset without consent of new owner
The buyer(new owner) can not list/relist the nft because of the way the functions are implemented. This will make the asset useless and means loss of funds for the buyer.
see above
Manual Review
update listings mapping to make sure the previous creator can not control the asset and also adjust the list() or relist() methods accordingly so that the new owner can use the asset for future listings
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.