Immunefi Audit Competitions

Firelight

Reports by Severity

Low

59967 - [SC - Low] broken historical period calculation
59937 - [SC - Low] periodattimestamp uses current time instead of inputtimestamp returning wrong period
59928 - [SC - Low] incorrect period calculation periodattimestamp function
59879 - [SC - Low] logic bug in periodattimestamp
59852 - [SC - Low] incorrect period calculation inside periodattimestamp resulting in returning period now instead of period at given timestamp
59820 - [SC - Low] periodattimestamp returns current period instead of historical period
59740 - [SC - Low] periodattimestamp provides period of current timestamp even for different timestamps
59728 - [SC - Low] underflow issue leading to a periodattimestamp dos
59715 - [SC - Low] periodattimestamp will return different period for the same timestamp input
59691 - [SC - Low] missing disableinitializers allows direct implementation initialization leading to vault takeover
59635 - [SC - Low] timestamp agnostic periodattimestamp misreports historical periods breaking time locked logic
59605 - [SC - Low] logic error in periodattimestamp returns incorrect periods
59559 - [SC - Low] period calculation does not use provided timestamp in periodattimestamp
59533 - [SC - Low] firelightvault sol periodattimestamp will return an incorrect period number due to flawed logic
59467 - [SC - Low] periodattimestamp ignores input parameter
59445 - [SC - Low] periodattimestamp does not work as expected
59422 - [SC - Low] periodattimestamp ignores the supplied timestamp
59385 - [SC - Low] timestamp ignored current block time used
59371 - [SC - Low] avoid leaving a vault contract uninitialized
59369 - [SC - Low] the function periodattimestamp uses the current timestamp instead of provided timestamp causing incorrect period calculation
59355 - [SC - Low] periodattimestamp ignores the input timestamp and returns the wrong period for non current timestamps
59335 - [SC - Low] periodattimestamp function returns current period instead of queried period leading to temporary freezing of funds
59334 - [SC - Low] periodAtTimestamp function uses current timestamp instead of input parameter, causing incorrect period calculation for historical or future queries
59298 - [SC - Low] function periodattimestamp ignores the input timestamp returning the current period instead
59296 - [SC - Low] periodattimestamp uint48 timestamp ignores its parameter and always returns the current period
59280 - [SC - Low] periodattimestamp uint48 timestamp ignores timestamp and return incorrect values when it is not time timestamp
59236 - [SC - Low] implementation contract lacks initializer protection
59235 - [SC - Low] firelight vault deviation from security best practice of locking down implementation logic
59226 - [SC - Low] logic flaw in periodattimestamp function breaks historical queries returning current period instead
59179 - [SC - Low] periodattimestamp bug returns current period for all timestamps
59168 - [SC - Low] incorrect time semantics in periodattimestamp cause off chain miscalculations and data inconsistency
59115 - [SC - Low] periodattimestamp function is incorrectly implemented and always returns period at current timestamp
59100 - [SC - Low] periodattimestamp returns current period instead of queried historical period
59091 - [SC - Low] [LOW]: FirelightVault.sol Implementation Contract Does Not Disable Initializers
59054 - [SC - Low] periodattimestamp returns incorrect period number
59031 - [SC - Low] periodattimestamp returns incorrect period numbers for non current timestamps
59023 - [SC - Low] unprotected implementation contract initializer allows unauthorized admin role assignment leading to potential governance manipulation
59007 - [SC - Low] periodattimestamp returns current period instead of historical
58993 - [SC - Low] incorrect timestamp calculation in periodattimestamp leads to broken historical period lookups
58992 - [SC - Low] the firelightvault contract doesn t call disableinitializers in its construcotor

Insight

Reports by Type

Smart Contract