Reproduced Exploit
Rubicon — Opening a position reuses prior collateral for borrowing
openPosition borrow budget uses _maxBorrow which includes residual capacity from prior positions on the shared Position account.
Chain
Other
Category
untagged
Date
Apr 2023
Source
AuditVault
EVM Playground
Source-level debugger — step opcodes and Solidity in sync
The attack is replayed in an in-browser EVM preloaded with the exact dumped fork state. The execution tree shows every call; step by Solidity line or by opcode across all depths — source, Stack, Memory, Storage, Balances (native / ERC-20 / NFT), Transient storage and Return value stay in sync. Click a tree node, opcode, or source line to jump. No backend, no live RPC.
Source & credit. Reproduction of a public audit finding curated by AuditVault — the original finding: 48952-h-13-when-opening-a-position-the-collateral-of-the-previous. Standalone Foundry PoC and full write-up: 48952-h-13-when-opening-a-position-the-collateral-of-the-previous_exp in the
evm-hack-registrymirror.
Vulnerability classes: liquidation-logic · direct-drain · account-ownership
Reproduction: self-contained Foundry PoC with only
forge-std— no fork, no RPC. Full trace: output.txt. PoC: test/48952-h-13-when-opening-a-position-the-collateral-of-the-previous_exp.sol.
Key info#
| Impact | HIGH — Second openPosition consumes residual borrow room and can hit liquidation threshold |
| Protocol | Rubicon |
| Bug class | liquidation-logic · direct-drain · account-ownership |
| Finding | Code4rena 2023-04-rubicon · #48952 · H-13 · reporter cccz |
| Report | code4rena.com/reports/2023-04-rubicon |
| Source | AuditVault |
| Status | Confirmed. Reproduced as a standalone local synthetic. |
| Compiler | ^0.8.24 (PoC) |
TL;DR#
openPosition borrow budget uses _maxBorrow which includes residual capacity from prior positions on the shared Position account.
The vulnerable code#
See synthetic test/48952-h-13-when-opening-a-position-the-collateral-of-the-previous.sol (@> VULN markers).
Fix: Do not use prior-position residual capacity when sizing a new open.
Root cause#
openPosition borrow budget uses _maxBorrow which includes residual capacity from prior positions on the shared Position account.
Preconditions#
Protocol deployed with the vulnerable code paths from the Code4rena contest.
Attack walkthrough#
See PoC run() and output.txt.
Diagrams#
Impact#
Second openPosition consumes residual borrow room and can hit liquidation threshold
Taxonomy#
genome: liquidation-logic · direct-drain · account-ownershipseverity/high·platform/code4rena
Sources#
- AuditVault finding #48952
- Code4rena report 2023-04-rubicon
- Repo@commit: code-423n4/2023-04-rubicon · contracts/utilities/poolsUtility/Position.sol ~L537-L550
Sources & further analysis#
Reproductions & code
- Standalone PoC + full trace: 48952-h-13-when-opening-a-position-the-collateral-of-the-previous_exp (evm-hack-registry mirror).
- AuditVault finding: 48952-h-13-when-opening-a-position-the-collateral-of-the-previous.
Alerts & third-party analyses
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.