Submitted by Trust, also found by subtle77, wagmi, Madalad, Matin, mookimgo, evan, Apocalypto, kaliberpoziomka8552, poirots, aga7hokakological, and yixxas
In VRFNFtRandomDraw\.sol initialize(), the MONTHINSECONDS variable is used to validate two values:
The issue is that MONTHINSECONDS is calculated incorrectly:
MONTHINSECONDS multiplies by 7 incorrectly, as it was copied from WEEKINSECONDS. Therefore, actual seconds calculated is equivalent of 7 months.
Therefore, recoverTimelock can be up to a non-sensible value of 7 years, and re-draws every up to 7 months.
Protocol safeguards for time durations are skewed by a factor of 7. Protocol may potentially lock NFT for period of 7 years.
Fix MONTHINSECONDS calculation:
uint256 immutable MONTH_IN_SECONDS = (3600 * 24) * 30;
iainnash (Forgeries) confirmed 
For this contest, 27 reports were submitted by wardens detailing low risk and non-critical issues. The report highlighted below by poirots received the top score from the judge.
The following wardens also submitted reports: deliriusz,
Aymen0909,
adriro,
zzykxx,
IllIllI,
Zarf,
ayeslick,
Madalad,
0xAgro,
Deivitto,
caventa,
immeas,
shark,
obront,
0xdeadbeef0x,
petersspetrov,
Bobface,
rvierdiiev,
0x1f8b,
Ruhum,
RaymondFam,
9svR6w,
cccz,
Bnke0x0,
oyc_109, and
Rolezn
.
