Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QA Report #144

Open
code423n4 opened this issue Jul 17, 2022 · 1 comment
Open

QA Report #144

code423n4 opened this issue Jul 17, 2022 · 1 comment
Labels
bug Something isn't working QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax

Comments

@code423n4
Copy link
Contributor

Zero address checks

Contract:
https://github.com/code-423n4/2022-07-yield/blob/main/contracts/Witch.sol#L176

Issue:
Check that auctioneer address is not 0. This mean the funds would be lost while paying the auctioneer cut once someone pay the debt

Recommendation:
Add below check in auction function

require(to!=address(0), "Invalid address");

Add pause feature if under attack

Contract:
https://github.com/code-423n4/2022-07-yield/blob/main/contracts/Witch.sol

Issue:
If contract is under attack and Auctioned Vault interaction for buying collateral need to be stopped, then currently there is no way.

Recommendation:
Add a pause modifier which allows Admin to stop interaction with Auctioned Vault function like payBase in case of emergency

Ignore pair on ongoing auction has no impact

Contract:
https://github.com/code-423n4/2022-07-yield/blob/main/contracts/Witch.sol#L150

Issue:
If setIgnoredPair function is called to ignore a pair on which a auction is already live then it has no impact on live auction

Recommendation:
Display an error to Admin mentioning that pair is already running live auction in a vault. If still required then have a boolean param which can forcefully ignore this pair

@code423n4 code423n4 added bug Something isn't working QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax labels Jul 17, 2022
code423n4 added a commit that referenced this issue Jul 17, 2022
@alcueca
Copy link
Collaborator

alcueca commented Jul 22, 2022

One useful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
Projects
None yet
Development

No branches or pull requests

2 participants