The creator sets the campaign deadline (README: "Sets campaign deadline"). The dealine_set flag and the DeadlineAlreadySet error exist to lock the deadline after the first call. The deadline closes contributions (L29) and opens refunds (L69), so contributors rely on it when they deposit.
set_deadline() reverts only when dealine_set is true, but nothing ever sets it to true. fund_create writes false (L20), and set_deadline writes only fund.deadline (L61). The value is not validated either, so it accepts:
0, which the program treats as "no deadline";
a timestamp in the past;
u64::MAX.
The creator can therefore change the deadline any number of times, at any moment, after contributors have committed SOL. DeadlineAlreadySet can never be returned.
Likelihood:
It needs the creator to act against contributors. Anyone can be a creator, and the README does not make creators trusted toward contributors. Each change is one set_deadline() call that can be sent at any time.
Reopening an expired campaign and cutting a running one short both work on the code exactly as deployed, with no other bug involved.
Impact:
After the advertised deadline has passed and contributions are closed, the creator can reopen the campaign with a future value or with 0 and keep collecting SOL. A past value ends a running campaign early, so later contributions revert. Contributors cannot rely on the deadline they saw when they deposited.
Once contribute() records contribution amounts (a separate one-line fix), the creator can move the deadline to u64::MAX just before it expires and block every refund indefinitely. In the PoC, refunds revert with DeadlineNotReached 1 second, 1 year and 100 years after the original deadline, while an identical honest fund refunds normally. Only the creator can reopen refunds, by calling set_deadline(0).
Three live tests run the unmodified program on unmodified state. The fourth is a latent test that pre-loads the Contribution record, as in the refund-gate finding.
A non-creator's call fails with ConstraintHasOne (2001). The creator then calls set_deadline six times in a row with now + 60 s, now + 10 years, 0, 1, u64::MAX and now + 7 days. All six succeed, each value is stored as given, and dealine_set stays false.
After the deadline has passed, contribute() reverts with DeadlineReached (6001). The creator moves the deadline 30 days later, and Bob's 3 SOL contribution is accepted. When that deadline also passes, set_deadline(0) reopens the campaign again.
On day 0 of a 30-day campaign the creator sets the deadline to 1 (in 1970), and Bob's contribution reverts with DeadlineReached.
Latent: two identical funds each have a 5 SOL backer, and 60 seconds before the deadline the creator sets one fund's deadline to u64::MAX.
One second after the deadline, the honest fund refunds 5 SOL.
The rigged fund's refund reverts with 6002 at that moment, a year later and 100 years later.
The rigged fund still accepts contributions 100 years on.
After the creator calls set_deadline(0), the refund goes through.
Run from the repository root. Everything before the cd line is a one-time setup; save the file above as programs/rustfund/tests/poc_RF-04.rs before running the last line:
Result: test result: ok. 4 passed; 0 failed. Key log lines:
Lock the deadline after the first call and require it to be in the future. If the deadline must not be set after contributions arrive, also require fund.amount_raised == 0 at this point.
The `set_deadline()` function in the `rustfund` program contains a vulnerability that allows campaign creators to manipulate deadlines indefinitely. While the function correctly checks if `fund.dealine_set` is true before allowing the deadline to be changed, it never sets this flag to true after setting the deadline. ```rust pub fn set_deadline(ctx: Context<FundSetDeadline>, deadline: u64) -> Result<()> { let fund = &mut ctx.accounts.fund; if fund.dealine_set { return Err(ErrorCode::DeadlineAlreadySet.into()); } fund.deadline = deadline; Ok(()) } ``` The function is missing a crucial line to update the flag: `fund.dealine_set = true;` This oversight bypasses a key safeguard intended to prevent creators from manipulating deadlines after they've been set. According to the project documentation, this flag is meant to enforce deadline immutability, which is an essential part of the platform's trust model. ### Impact 1. **Refund evasion**: Creators can prevent users from obtaining refunds by continually extending the deadline whenever it approaches. This directly undermines the project's advertised "Refund Mechanism" which promises that "Contributors can get refunds if deadlines are reached and goals aren't met." 2. **Fund locking**: Contributors' funds can be effectively locked indefinitely, as the refund function is contingent upon the deadline being reached: ```rust if ctx.accounts.fund.deadline != 0 && ctx.accounts.fund.deadline > Clock::get().unwrap().unix_timestamp.try_into().unwrap() { return Err(ErrorCode::DeadlineNotReached.into()); } ``` ### Proof of Concept (PoC) The following test demonstrates how a creator can set the deadline multiple times, effectively bypassing the intended deadline immutability: ```javascript import * as anchor from "@coral-xyz/anchor"; import { Program } from "@coral-xyz/anchor"; import { Rustfund } from "../target/types/rustfund"; import { assert } from "chai"; describe("VULN-02: set_deadline vulnerability", () => { // Configures the provider to use the local cluster const provider = anchor.AnchorProvider.env(); anchor.setProvider(provider); const program = anchor.workspace.Rustfund as Program<Rustfund>; // Test variables const fundName = "TestFund"; const description = "Testing deadline vulnerability"; const goal = new anchor.BN(1000000); let fundPda: anchor.web3.PublicKey; it("Allows you to modify the deadline several times", async () => { // Derivation of PDA address for financing account [fundPda] = await anchor.web3.PublicKey.findProgramAddress( [Buffer.from(fundName), provider.wallet.publicKey.toBuffer()], program.programId ); // Fund creation await program.rpc.fundCreate(fundName, description, goal, { accounts: { fund: fundPda, creator: provider.wallet.publicKey, systemProgram: anchor.web3.SystemProgram.programId, }, }); // First deadline assignment const deadline1 = new anchor.BN(Math.floor(Date.now() / 1000) + 3600); // 1 hour in the future await program.rpc.setDeadline(deadline1, { accounts: { fund: fundPda, creator: provider.wallet.publicKey, }, }); // Second deadline assignment (which should not be possible if the flag is set to true) const deadline2 = new anchor.BN(Math.floor(Date.now() / 1000) + 7200); // 2 hours into the future await program.rpc.setDeadline(deadline2, { accounts: { fund: fundPda, creator: provider.wallet.publicKey, }, }); // Check that the deadline has been updated to the second value const fundAccount = await program.account.fund.fetch(fundPda); assert.ok( fundAccount.deadline.eq(deadline2), "The deadline may have been modified several times, but vulnerability presents" ); }); }); ``` Save the above test as, for example, tests/02.ts in your project's test directory and run the test : ```Solidity anchor test ``` ### Concrete Impact Example To illustrate the real-world impact of this vulnerability, consider this scenario: - A creator launches a campaign to fund a project with a goal of 100 SOL - The creator sets an initial deadline of 30 days - Contributors collectively deposit 80 SOL (below the goal) - As the deadline approaches, the creator realizes they won't reach the goal - Instead of allowing refunds as promised, the creator extends the deadline by another 30 days - This pattern can repeat indefinitely, effectively locking contributor funds - Even if contributors try to request refunds, they'll be rejected with "DeadlineNotReached" errors ### Recommendation The fix for this vulnerability is straightforward. The `set_deadline()` function should be modified to set the `dealine_set` flag to true after setting the deadline: ```rust pub fn set_deadline(ctx: Context<FundSetDeadline>, deadline: u64) -> Result<()> { let fund = &mut ctx.accounts.fund; if fund.dealine_set { return Err(ErrorCode::DeadlineAlreadySet.into()); } fund.deadline = deadline; fund.dealine_set = true; // Add this line to fix the vulnerability Ok(()) } ```
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.