Flare is the blockchain for data. It is a layer 1, EVM smart contract platform designed to expand the utility of blockchain by delivering data certainty for dApp builders.
FAssets is a trustless, over-collateralized bridge built on Flare that connects non smart contract networks to Flare/Songbird. It enables the creation of wrapped tokens (FAssets) for assets like BTC, DOGE and XRP.
Triaged by Immunefi
PoC Required
Arbitration enabled
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
FAssets:
- Impacts achieved with frontrunning attacks will have severity lowered by one level.
- Impacts requiring malicious agent actions will have severity lowered by one level.
- Theft, freezing or loss of dust amounts of funds below the value of $1000 will be considered as griefing.
- Loss of funds caused by penalisation is not considered as theft of funds.
Ability to exfiltrate a validator's staking keys (TLS or BLS) without direct machine access
Unauthorized minting of tokens
Network not being able to confirm new transactions (total network shutdown)
Unintended permanent chain split requiring hard fork (network partition requiring hard fork)
Direct loss of funds
Permanent freezing of funds (fix requires hardfork)
Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Permanent freezing of funds
Protocol insolvency
Execute arbitrary system commands
Retrieve sensitive data/files from a running server, such as:
- /etc/shadow
- database passwords
- blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)
Out of scope
These impacts are out of scope for this bug bounty program.
-
Impacts caused by vulnerabilities disclosed in the repositories of assets in scope, or in those of any dependencies.
-
Impacts from Denial-of-Service attacks
-
Consensus liveness failure requiring network control.
-
Unintended node behavior caused by local disk failures.
-
Unintended node behavior caused by unusual node configuration deviating from best practices for node configurations.
-
Compile time or runtime errors due to using unsupported hardware or operating systems.
-
Inability to automatically perform NAT-hole punching on specific router hardware.
-
FAssets: any attacks related to FBTC, FDOGE, or UTXO-based logic in general, are out of scope.
All categories
- Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
- Impacts caused by attacks requiring access to leaked keys/credentials
- Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
- Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
- Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
- Best practice recommendations
- Feature requests
- Impacts on test files and configuration files unless stated otherwise in the bug bounty program
- Impacts requiring phishing or other social engineering attacks against project's employees and/or customers