Skip to content

Actions: code-423n4/2024-10-kleidi-findings

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
597 workflow runs
597 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Some bytes may be emitted when we check the call data Repo Moderator #497: Issue #48 labeled by c4-judge
November 4, 2024 19:15 3s
November 4, 2024 19:15 3s
Calldata checks require an unvalidated byte in between calldata segments which leads to flawed validation Repo Moderator #496: Issue #31 labeled by c4-judge
November 4, 2024 19:15 2s
November 4, 2024 19:15 2s
It's impossible to add a calldata check for neighboring byte portions (and more implications) Repo Moderator #495: Issue #47 unlabeled by c4-judge
November 4, 2024 19:15 3s
November 4, 2024 19:15 3s
Some bytes may be emitted when we check the call data Repo Moderator #494: Issue #48 labeled by c4-judge
November 4, 2024 19:15 3s
November 4, 2024 19:15 3s
addCalldataCheck() will always revert when more than 1 parameter is whitelisted for the callDatas. Repo Moderator #493: Issue #35 unlabeled by c4-judge
November 4, 2024 19:15 2s
November 4, 2024 19:15 2s
Some bytes may be emitted when we check the call data Repo Moderator #492: Issue #48 unlabeled by c4-judge
November 4, 2024 19:15 2s
November 4, 2024 19:15 2s
If the recovery owner is compromised, the wallet can be stolen and drained by the attacker in certain circumstances Repo Moderator #491: Issue #23 labeled by c4-judge
November 4, 2024 19:15 2s
November 4, 2024 19:15 2s
executeRecoverySpell() can revert due to check in OwnerManager.swapOwner() and causes safe to be compromised Repo Moderator #490: Issue #30 labeled by c4-judge
November 4, 2024 19:15 2s
November 4, 2024 19:15 2s
The same address in original owner set and recovery owner set can lead to permanent DoS Repo Moderator #489: Issue #33 labeled by c4-judge
November 4, 2024 19:15 2s
November 4, 2024 19:15 2s
Immutable Recovery threshold limits flexibility, risking loss of Safe access in critical scenarios Repo Moderator #488: Issue #27 labeled by c4-judge
November 4, 2024 19:15 2s
November 4, 2024 19:15 2s
Missing New Recovery Spell Replacement in the Recovery Process, To Ensure Safe Can Be Saved Again Repo Moderator #487: Issue #39 labeled by c4-judge
November 4, 2024 19:15 2s
November 4, 2024 19:15 2s
Calldata check can not be added for adjacent parameters Repo Moderator #486: Issue #26 labeled by c4-judge
October 31, 2024 08:03 2s
October 31, 2024 08:03 2s
Unable to create a calldata check immediately adjacent to an existing one Repo Moderator #485: Issue #29 labeled by c4-judge
October 31, 2024 08:03 2s
October 31, 2024 08:03 2s
Calldata checks require an unvalidated byte in between calldata segments which leads to flawed validation Repo Moderator #484: Issue #31 labeled by c4-judge
October 31, 2024 08:03 2s
October 31, 2024 08:03 2s
addCalldataCheck() will always revert when more than 1 parameter is whitelisted for the callDatas. Repo Moderator #483: Issue #35 labeled by c4-judge
October 31, 2024 08:03 2s
October 31, 2024 08:03 2s
It's impossible to add a calldata check for neighboring byte portions (and more implications) Repo Moderator #482: Issue #47 labeled by c4-judge
October 31, 2024 08:03 2s
October 31, 2024 08:03 2s
Some bytes may be emitted when we check the call data Repo Moderator #481: Issue #48 labeled by c4-judge
October 31, 2024 08:03 2s
October 31, 2024 08:03 2s
The calldata checks which don't overlap partially can't be added. Repo Moderator #480: Issue #50 labeled by c4-judge
October 31, 2024 08:02 2s
October 31, 2024 08:02 2s
Invalid Validation in _addCalldataCheck is causing dead bytes in payload Repo Moderator #479: Issue #54 labeled by c4-judge
October 31, 2024 08:02 2s
October 31, 2024 08:02 2s
Potential DoS Due to Retrieving Large Number of Proposals or Calldatas in Functions that Modify State Repo Moderator #478: Issue #38 labeled by c4-judge
October 31, 2024 08:00 2s
October 31, 2024 08:00 2s
The pause function in the Timelock contract could be temporarily subjected to a DoS attack due to the unbounded iteration over the liveProposals array. Repo Moderator #477: Issue #51 labeled by c4-judge
October 31, 2024 08:00 2s
October 31, 2024 08:00 2s
Potential Denial-of-Service (DoS) in Timelock pause Function Repo Moderator #476: Issue #41 labeled by c4-judge
October 31, 2024 07:59 2s
October 31, 2024 07:59 2s
Guardian can be DoSed by submitting many transactions at once Repo Moderator #475: Issue #4 labeled by c4-judge
October 31, 2024 07:59 2s
October 31, 2024 07:59 2s
Attackers that have compromised signer keys can financially overwhelm the protocol to take it over Repo Moderator #474: Issue #5 labeled by c4-judge
October 31, 2024 07:59 2s
October 31, 2024 07:59 2s
Pause function can be bricked Repo Moderator #473: Issue #25 labeled by c4-judge
October 31, 2024 07:58 2s
October 31, 2024 07:58 2s