Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
open-web3-stack/open-runtime-module-library
master @ 33bc94a
15
Fixes
0
CVEs
HIGH
Peak severity
Highlights
Logic Error: 11 prior fixes. Scrutinize any change in this area.
tokens: most-fixed (6 issues). Treat as high-risk during review.
9 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Logic Error: Inconsistent enforcement of existential deposit (ED) validations during state transfers, deposits, and dust calculations can result in sub-threshold dust accounts and untracked changes to total token issuance. Ensure strict validation checks are consistently executed in all mutating paths.
Logic Error: Triggering side effects, callbacks, or mutation hooks before state modifications are committed can lead to reentrancy vulnerabilities or inconsistent storage states during execution. Hook dispatches must be sequenced carefully after state resolution.
Data Integrity: Complex balance-shifting actions, such as account merging and cross-chain transfers, are vulnerable to partial state updates if execution fails mid-transaction. These workflows must be marked with transactional attributes to ensure atomic rollbacks.