`Snow::s_earnTimer` is a single global variable instead of per-address, causing `earnSnow` and `buySnow` to lock out all other users for a week after any single call
`Snow::earnSnow`'s cooldown is enforced via `s_earnTimer`, a single `uint256` rather than a per-address `mapping`. As a result, the cooldown check does not check if that caller farmed in the last week, but rather checks if anyone farmed or bought in the last week.
Likelihood:
High. This is not an edge case. It is the default, guaranteed outcome the moment more than one address interacts with earnSnow/buySnow within the same week, which is the expected norm for any protocol with real usage.
Impact:
Since `s_earnTimer` is not keyed by address, the very first successful call to `earnSnow` by any address resets a global timer. Every call to `earnSnow` by any other address, regardless of whether that address has ever farmed before, reverts with `S__Timer()` until a full week has elapsed since that single global timestamp. `buySnow` compounds this: since it also writes `s_earnTimer = block.timestamp` on every successful purchase, a paid purchase by any user re-locks `earnSnow` for everyone else for another full week. In practice, this means at most one successful `earnSnow` or `buySnow` can occur across the entire protocol per week: not one per user per week. Any address can call `earnSnow` or `buySnow` repeatedly (subject only to the same global cooldown) purely to keep resetting the timer and permanently deny the free-farming mechanic to everyone else, at minimal cost to themselves.
Add the following variables to the `TestSnow.t.sol` test suite:
Initialize the variables in the `setUp` function:
Add the following tests to the test suite:
Run the tests in the terminal:
If the tests pass the contract is capable of being exploited through DDoS attack.
Change the earn timer to a per-address mapping. Moving from a single uint256 to store the timer to a mapping allows for each user to have an individual earn timer, and prevents one user's actions from affecting another's:
## Description: The `Snow::buySnow` function contains a critical flaw where it resets a global timer `(s_earnTimer)` to the current block timestamp on every invocation. This timer controls eligibility for free token claims via `Snow::earnSnow()`, which requires 1 week to pass since the last timer reset. As a result: Any token purchase `(via buySnow)` blocks all free claims for all users for 7 days Malicious actors can permanently suppress free claims with micro-transactions Contradicts protocol documentation promising **"free weekly claims per user"** ## Impact: * **Complete Denial-of-Service:** Free claim mechanism becomes unusable * **Broken Protocol Incentives:** Undermines core user acquisition strategy * **Economic Damage:** Eliminates promised free distribution channel * **Reputation Harm:** Users perceive protocol as dishonest ```solidity function buySnow(uint256 amount) external payable canFarmSnow { if (msg.value == (s_buyFee * amount)) { _mint(msg.sender, amount); } else { i_weth.safeTransferFrom(msg.sender, address(this), (s_buyFee * amount)); _mint(msg.sender, amount); } @> s_earnTimer = block.timestamp; emit SnowBought(msg.sender, amount); } ``` ## Risk **Likelihood**: • Triggered by normal protocol usage (any purchase) • Requires only one transaction every 7 days to maintain blockage • Incentivized attack (low-cost disruption) **Impact**: • Permanent suppression of core protocol feature • Loss of user trust and adoption • Violates documented tokenomics ## Proof of Concept **Attack Scenario:** Permanent Free Claim Suppression * Attacker calls **buySnow(1)** with minimum payment * **s\_earnTimer** sets to current timestamp (T0) * All **earnSnow()** calls revert for **next 7 days** * On day 6, attacker repeats **buySnow(1)** * New timer reset (T1 = T0+6 days) * Free claims blocked until **T1+7 days (total 13 days)** * Repeat step **4 every 6 days → permanent blockage** **Test Case:** ```solidity // Day 0: Deploy contract snow = new Snow(...); // s_earnTimer = 0 // UserA claims successfully snow.earnSnow(); // Success (first claim always allowed) // Day 1: UserB buys 1 token snow.buySnow(1); // Resets global timer to day 1 // Day 2: UserA attempts claim snow.earnSnow(); // Reverts! Requires day 1+7 = day 8 // Day 7: UserC buys 1 token (day 7 < day 1+7) snow.buySnow(1); // Resets timer to day 7 // Day 8: UserA retries snow.earnSnow(); // Still reverts! Now requires day 7+7 = day 14 ``` ## Recommended Mitigation **Step 1:** Remove Global Timer Reset from `buySnow` ```diff function buySnow(uint256 amount) external payable canFarmSnow { // ... existing payment logic ... - s_earnTimer = block.timestamp; emit SnowBought(msg.sender, amount); } ``` **Step 2:** Implement Per-User Timer in `earnSnow` ```solidity // Add new state variable mapping(address => uint256) private s_lastClaimTime; function earnSnow() external canFarmSnow { // Check per-user timer instead of global if (s_lastClaimTime[msg.sender] != 0 && block.timestamp < s_lastClaimTime[msg.sender] + 1 weeks ) { revert S__Timer(); } _mint(msg.sender, 1); s_lastClaimTime[msg.sender] = block.timestamp; // Update user-specific timer emit SnowEarned(msg.sender, 1); // Add missing event } ``` **Step 3:** Initialize First Claim (Constructor) ```solidity constructor(...) { // Initialize with current timestamp to prevent immediate claims s_lastClaimTime[address(0)] = block.timestamp; } ```
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.