Maia DAO — redeem() in beforeRedeem uses the wrong owner parameter

Source & credit. Reproduction of a public audit finding curated by AuditVault — the original finding: 26041-h-07-redeem-in-beforeredeem-is-using-the-wrong-owner-paramet. Standalone Foundry PoC and full write-up: 26041-h-07-redeem-in-beforeredeem-is-using-the-wrong-owner-paramet_exp in the evm-hack-registry mirror.

Vulnerability classes: see taxonomy below

Reproduction: a self-contained Foundry PoC that compiles & runs in an isolated project with only forge-std — no fork, no RPC, no anvil_state. Full trace: output.txt. PoC: test/26041-h-07-redeem-in-beforeredeem-is-using-the-wrong-owner-paramet_exp.sol.

Key info#


Impact	HIGH — beforeRedeem(receiver) accrues the wrong address; owner shares burned without accrue; 100 RWD stranded
Protocol	Maia DAO
Finding	Code4rena · reporter bin2chen
Report	https://code4rena.com/reports/2023-05-maia
Source	AuditVault
Status	Audit finding — reproduced as a standalone local PoC.
Compiler	`^0.8.24` (PoC)

This is an audit finding, not a historical on-chain incident.

TL;DR#

redeem burns _owner shares but calls beforeRedeem(receiver).\n2. flywheel.accrue hits receiver (0 shares).\n3. Owner never accrues; rewards stranded in flywheel.

Diagrams#

flowchart TD A[Setup vulnerable state] --> B[Trigger vulnerable path] B --> C[Harm asserted in run]

Impact#

beforeRedeem(receiver) accrues the wrong address; owner shares burned without accrue; 100 RWD stranded

Sources#

AuditVault finding
Code4rena report
Reduced synthetic: test/26041-h-07-redeem-in-beforeredeem-is-using-the-wrong-owner-paramet.sol (C2 local-deploy)

Sources & further analysis#

Reproductions & code

Standalone PoC + full trace: 26041-h-07-redeem-in-beforeredeem-is-using-the-wrong-owner-paramet_exp (evm-hack-registry mirror).
AuditVault finding: 26041-h-07-redeem-in-beforeredeem-is-using-the-wrong-owner-paramet.

Alerts & third-party analyses

Web3Sec X hacked database: search.
Rekt leaderboard: search.
Solodit incident search: search.

These dashboards index community alerts tweets, post-mortems, and independent write-ups. Reach them through the protocol name above to cross-check this reproduction against other analyses.

Source-level debugger — step opcodes and Solidity in sync