Security context

Highlights

Auth Bypass: 40 prior fixes. Scrutinize any change in this area.

DepositSecurityModule.sol: most-fixed (9 issues). Treat as high-risk during review.

48 high-severity fixes in this history; regressions here are high-impact.

Recurring patterns

Auth Bypass: Critical initialization flows and administrative capabilities (such as report, rebalance, and token recovery) were exposed to direct invocation or bypasses. StakingVault implementations could be initialized directly by bypassing proxy checks, or compromised via unvalidated recovery of ETH using specific token representations.

Auth Bypass: The deposit enforcement and pause mechanisms relied on multi-signature verification patterns that historically permitted quorum bypasses. Specifically, vulnerabilities arose from signature replay across networks (due to missing chain IDs), lack of zero-blockhash checks allowing expired signatures, and zero-signature bypasses when quorum boundaries were misconfigured.

Auth Bypass: The multi-confirmation consensus mechanism utilized for highly sensitive DAO operations could be bypassed entirely by submitting an empty array of roles, which allowed immediate execution without validations. Additionally, using Keccak256 hashes instead of raw transaction data for confirmation tracking introduced potential collision and replay vectors.