Submission Details
Severity:
No access control on `receive`/`payable fallback`
Summary
No access control on receive/payable fallback
Vulnerability Details
Having no access control on the function means that someone may send Ether to the contract, and have no way to get anything back out, which is a loss of funds. If the concern is having to spend a small amount of gas to check the sender against an immutable address, the code should at least have a function to rescue unused Ether.
Impact
Instances (2):
File: contracts/LiquidationPoolManager.sol
31: receive() external payable {}
File: contracts/SmartVaultV3.sol
125: receive() external payable {}
Tools Used
Recommendations
Updates
Lead Judging Commences
hrishibhat over 1 year ago
Submission Judgement Published Reason: Non-acceptable severity
Assigned finding tags:
informational/invalid
Prize pool breakdown
Total prize
20,000 USDC
nSLOC
60933 USDC / LOC
17,500 USDC
2,500 USDC
Live
The contest is live. Earn rewards by submitting a finding.
Appeals
This is your time to appeal against judgements on your submissions.
Appeals Review
Appeals are being carefully reviewed by our judges.