Paladin - Warden Pledges contest - jwood's results

A governance lending protocol transforming users voting power into a new money lego.

General Information

Platform: Code4rena

Start Date: 27/10/2022

Pot Size: $33,500 USDC

Total HM: 8

Participants: 96

Period: 3 days

Judge: kirk-baird

Total Solo HM: 1

Id: 176

League: ETH

Paladin

Findings Distribution

Researcher Performance

Rank: 70/96

Findings: 1

Award: $19.64

QA:
grade-b

🌟 Selected for report: 0

🚀 Solo Findings: 0

Lines of code

https://github.com/code-423n4/2022-10-paladin/blob/d6d0c0e57ad80f15e9691086c9c7270d4ccfe0e6/contracts/WardenPledge.sol#L653-L661

Vulnerability details

Impact

Some tokens have multiple entrypoints, eg. address(a) and address(b) which both use the same balance.

When one of address are used as the reward token eg address(a), the owner can sweep the tokens by calling recoverERC20() on address(b)

Proof of Concept

ERC token has two entrypoint addresses, address(a) and address(b)

  1. a pledge is created using address(a) which transfers in the reward token.

  2. owner can then call recoverERC20() on address(b) to sweep the reward token

#0 - Kogaroshi

2022-10-30T23:04:23Z

Duplicate of #16

#1 - kirk-baird

2022-11-10T21:40:38Z

I rate this as QA as it is a standard requirement when whitelisting tokens to whitelist both addresses.

#2 - c4-judge

2022-11-10T21:40:44Z

kirk-baird changed the severity to QA (Quality Assurance)

#3 - c4-judge

2022-11-11T23:54:03Z

kirk-baird marked the issue as grade-b

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