RustFund

Summary

A typo in the Fund Struct causes critical security failures that undermine the protocol’s integrity. The incorrectly named field, dealine_set, is never updated, allowing unauthorized modifications to the fund’s deadline. This single point of failure leads to two major issues:

1. State Tracking Failure: The flag intended to track whether a deadline has been set (deadline_set) is never updated, allowing repeated modifications.

2. Broken Access Control: The protocol’s enforcement of immutable deadlines is bypassed, allowing multiple calls to set_deadline.

By correcting this typo, both vulnerabilities are resolved.

Vulnerability Details

Root Cause Analysis

The Fund struct defines the flag as dealine_set (misspelled) instead of deadline_set. As a result:

• The function set_deadline incorrectly references dealine_setwhich is never set to true.

• The intended deadline_set flag remains false, allowing multiple deadline modifications.

Code Analysis

Current Code (Vulnerable)

Impact Analysis

Exploitation Scenario

1. An attacker (or even a legitimate user) calls set_deadline().

2. The function does not recognize that a deadline has been set (due to the typo).

3. The attacker can call set_deadline() repeatedly, modifying the deadline at will.

Recommended Fix

To resolve both issues, the typo must be corrected in the Fund struct and the set_deadline function.

Fixed Code

Conclusion

This vulnerability is a single point of failure affecting both state tracking and access control. Fixing the typo eliminates the risk of repeated modifications and restores protocol integrity. This issue is critical because it directly undermines the contract’s immutability guarantees. By applying this fix, the protocol ensures deadlines can only be set once, as intended.