Trail of Bits Discloses Provenance Blockchain Authorization Flaw
Security vulnerability exposed 82 mainnet asset accounts to potential takeover and unauthorized minting.
Quick Look
- Trail of Bits identified a security flaw in Provenance Blockchain affecting 82 asset accounts.
- The bug allowed unauthorized administrative control and minting due to a supply record mismatch.
- Patches were released in May and June to remediate the vulnerability.
AI-generated summary
Why It Matters
Provenance Blockchain uses 'markers' to govern token supply and permissions. A mismatch between bank module records and marker supply fields created an authorization loophole.
Trail of Bits disclosed a Provenance Blockchain authorization flaw that it said exposed 82 live mainnet asset accounts to takeover. A successful abuse could let someone mint an affected token or withdraw assets held in escrow.
Those special asset accounts, called markers, govern a token's supply, permissions, and escrow balance. The security firm said the flaw allowed a user who held none of a marker's tokens to take its admin, mint, and withdrawal permissions, then act on them in a second transaction.
The bug came from a mismatch between two records of token supply. For non-fixed markers, Provenance's bank module tracks live circulating supply, while the marker's supply field can remain at zero.
The authorization check read the stale marker field when testing whether an account held the entire supply. Because a new account's balance was also zero, the check treated zero as equal to zero and approved the permission change.
Trail of Bits said all 82 affected markers had zero stored supply while carrying real circulating supply or assets in escrow.
The disclosed affected nhash escrow totaled roughly 30 quadrillion nhash, worth about $500,000 at HASH prices when the issue was discovered. Three Provenance Blockchain Foundation programs held most of it: grant0051 held about 19.23 quadrillion nhash, provenance.validator.incentive.program held about 8.56 quadrillion, and grant0077 held about 2.49 quadrillion.
A distinct 74-marker token subset, included within the total of 82, faced unauthorized minting risk. It spanned bridged stablecoins and wrapped assets, consortium deposits, tokenized mortgage participations, and yield tokens.
Named examples included uusd.trading, uusdc.figure.se, nbtc.figure.se, cusd.deposit, cguaranteedrateomni, chomebridgeomni, nuva.ylds, and uylds.fcc.
Trail of Bits described a direct inflation risk for unrestricted coin-type markers. Restricted tokens with identity requirements faced supply-integrity and solvency risks even if an attacker could not freely transfer newly created units.
Trail of Bits said it discovered the flaw in March and reported it to Provenance on April 1. It said a zero-supply guard released with v1.28.0 on May 1 blocked the reported path against all 82 identified markers.
A second change made the authorization check read live supply from the bank module, and the project included it in v1.29.0 on June 8.
GitHub records show the code changes were merged and released. The Trail of Bits disclosure does not say whether chain analysis found unauthorized access, minting, or withdrawals, or whether it notified affected issuers and users.
Open Questions
- Was the vulnerability exploited by malicious actors?
- Were affected token issuers notified?
