Vader Protocol contest - JMukesh's results

Capital efficient liquidity protocol

General Information

Platform: Code4rena

Start Date: 22/04/2021

Pot Size: $120,000 USDC

Total HM: 41

Participants: 10

Period: 7 days

Judge: LSDan

Total Solo HM: 28

Id: 5

League: ETH

Vader Protocol

Findings Distribution

Researcher Performance

Rank: 9/10

Findings: 4

Award: $2,247.13

🌟 Selected for report: 3

🚀 Solo Findings: 0

Findings Information

🌟 Selected for report: jvaqa

Also found by: JMukesh

Labels

bug
duplicate
disagree with severity
3 (High Risk)
sponsor disputed

Awards

14.6655 VETH - $762.61

0.352 ETH - $879.93

External Links

Handle

JMukesh

Vulnerability details

Impact

its impact will be high since, collecting fee from user is one of the source of revenue. If user are able to bypass the fees collected by protocol then it will decrease the revenue

Proof of Concept

In Vether.sol https://github.com/code-423n4/2021-04-vader/blob/main/vader-protocol/contracts/Vether.sol#L93

function addExcluded(address excluded) public { mapAddress_Excluded[excluded] = true; }

this function can be called by anyone , due to which anyone can their map their own address. Since this address will be excluded, because of that _getFee(address, address, uint){} will return 0 fees which leads to bypass of transaction fees when it call transfer(address, uint){} function.

Tools Used

No tool used

Add access control modifier

#0 - Mervyn853

2021-04-25T00:00:16Z

strictly-scarce — 4/24/2021 at 10:33 PM Regarding Vader-Review, just FYI an older, incorrect, copy of Vether.sol was put into the repo. (it has some small variations in order to simplify testing code for Vader, which is the focus of the Repo).

The correct code deployed on Mainent () is available here: https://etherscan.io/address/0x4Ba6dDd7b89ed838FEd25d208D4f644106E34279#code

The incorrect, and not applicable, testing contract that was uploaded is here: https://github.com/code-423n4/2021-04-vader/blob/main/vader-protocol/contracts/Vether.sol

#1 - strictly-scarce

2021-04-25T09:49:30Z

The reason this deviation is for ease of testing in how the testing framework executes.

The correct deployed Vether contract does not have this issue.

REcommend: Close

#2 - Mervyn853

2021-05-01T08:48:29Z

Our decision matrix for severity:

0: No-risk: Code style, clarity, off-chain monitoring (events etc), exclude gas-optimisations 1: Low Risk: UX, state handling, function incorrect as to spec 2: Funds-Not-At-Risk, but can impact the functioning of the protocol, or leak value with a hypothetical attack path with stated assumptions, but external requirements 3: Funds can be stolen/lost directly, or indirectly if a valid attack path shown that does not have handwavey hypotheticals.

Recommended: 0

#3 - dmvt

2021-05-26T19:04:37Z

The warden should be paid out on this issue, in my opinion, because the code was included in the repo to be reviewed. The work to review the contract was done despite the fact that the team has addressed the issue and has already deployed vether.sol. I do not think that any issues related to Vether.sol should be included in the final report generated by @code423n4.

#4 - dmvt

2021-05-26T22:25:20Z

duplicate of #189

AuditHub

A portfolio for auditors, a security profile for protocols, a hub for web3 security.

Built bymalatrax © 2024

Auditors

Browse

Contests

Browse

Get in touch

ContactTwitter