Submitted by t0x1c, also found by ether_sky, peanuts, oakcobalt, IceBear, wangxx2026, 0xpiken, and 0xCiphky
ManagedWallet.sol states that:
However, the current 30-day wait period can be bypassed. 
The expected order by the protocol is:
To bypass the 30-day limitation, the following flow can be used:
Impact: Although the users believe that any changes to wallet address is going to have a timelock of 30 days as promised by the protocol, it really can be bypassed by the current admins/wallet addresses. This breaks the intended functionality implmentation.
Add the following inside 2024-01-salty/src/root_tests/ManagedWallet.t.sol and run with COVERAGE="yes" NETWORK="sep" forge test -vv --rpc-url https://rpc.sepolia.org/ --mt test_ManipulateActiveTimeLockBeforeProposingNewWallets:
Foundry
Inside receive() make sure an active proposal exists:
othernet-global (Salty.IO) confirmed and commented:
Status: Mitigation confirmed. Full details in reports from t0x1c, zzebra83, and 0xpiken.
For this audit, 57 reports were submitted by wardens detailing low risk and non-critical issues. The report highlighted below by juancito received the top score from the judge.
The following wardens also submitted reports: oakcobalt, J4X, peanuts, 7ashraf, niroh, ether_sky, 0xCiphky, t0x1c, Jorgect, 0xbepresent, 0xBinChook, Topmark, lsaudit, Bauchibred, 0xSmartContractSamurai, Tripathi, 0xMango, vnavascues, Arz, grearlake, Audinarey, Udsen, slvDev, pina, lanrebayode77, inzinko, sivanesh_808, KingNFT, jasonxiale, josephdara, IceBear, csanuragjain, The-Seraphs, 0x3b, Draiakoo, 0xpiken, wangxx2026, 0xRobocop, dharma09, Rolezn, ZanyBonzy, a3yip6, chaduke, codeslide, 0xHelium, b0g0, Banditx0x, djxploit, 0xOmer, Rhaydden, Kaysoft, eta, linmiaomiao, jesjupyter, 0xWaitress, and Tigerfrake.
