Vault share conversion or rounding breaks entitlement
Conversions, fees or rounding create an unintended claim on assets or an eligible loss under supported token behavior.
Candidate CWE: CWE-682
Test hypothesis#
In a local vault, compare ordinary round trips with minimal amounts, zero-supply state, direct donations and mixed supported decimals. Track independent asset/share balances and attacker cost.
Evidence required#
Units, initial supply, exact sequence, fees, rounding direction and bounded victim/protocol loss versus baseline.
Rule out false positives#
Expected rounding dust, unsupported token semantics and unprofitable scenarios without eligible harm do not establish the claimed exploit.
Playbook and command references#
- Contract state: authorization, callbacks and accounting — Turn protocol promises into explicit invariants and test realistic local operation sequences with independent accounting.
Find the associated command snippets
Referenced by these target playbooks#
Report checklist#
- Capture the affected version, configuration, identities, and object ownership.
- Preserve a valid baseline and a negative control.
- Reproduce the forbidden data access, action, or state change on controlled fixtures.
- Explain the intended security rule and why the observed behavior violates it.
- State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.
Conditional ATT&CK mapping#
No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.