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

Basket.sol#changePublisher() Insufficient input validation #61

Open
code423n4 opened this issue Oct 10, 2021 · 1 comment
Open

Basket.sol#changePublisher() Insufficient input validation #61

code423n4 opened this issue Oct 10, 2021 · 1 comment
Labels
1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Warden finding sponsor confirmed Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity")

Comments

@code423n4
Copy link
Contributor

Handle

WatchPug

Vulnerability details

As per the test, changePublisher to the current publisher should not be allowed:

https://github.com/code-423n4/2021-10-defiprotocol/blob/7ca848f2779e2e64ed0b4756c02f0137ecd73e50/contracts/test/Basket.test.js#L122-L122

let publisher = await basket.publisher();
expect(publisher).to.equal(addr2.address);

await expect(basket.connect(addr2).changePublisher(addr2.address)).to.be.reverted;

However, there is no such check to make sure that.

https://github.com/code-423n4/2021-10-defiprotocol/blob/7ca848f2779e2e64ed0b4756c02f0137ecd73e50/contracts/contracts/Basket.sol#L147-L148

function changePublisher(address newPublisher) onlyPublisher public override {
    require(newPublisher != address(0));

Recommendation

Change to:

function changePublisher(address newPublisher) onlyPublisher public override {
    require(newPublisher != address(0) && newPublisher != publisher);
@code423n4 code423n4 added 1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Warden finding labels Oct 10, 2021
code423n4 added a commit that referenced this issue Oct 10, 2021
@frank-beard frank-beard added the sponsor confirmed Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity") label Nov 6, 2021
@GalloDaSballo
Copy link
Collaborator

Agree with finding, because there's tets, hence proof that this is the desired functionality, the warden has proven that the code doesn't behave as the sponsor intended. Agree with the severity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Warden finding sponsor confirmed Sponsor agrees this is a problem and intends to fix it (OK to use w/ "disagree with severity")
Projects
None yet
Development

No branches or pull requests

3 participants