Citrea Web & Apps: Program info

Impacts in Scope

Below are the impacts accepted by default under this bug bounty program. Nevertheless, Citrea team is open to considering any impactful out-of-scope items on a case-by-case basis, following the Primacy of Impact spirit of this Program.

• Critical. Execute arbitrary system commands
• Critical. 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)
• Critical. Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as:
• Changing registration information
• Commenting
• Voting
• Making trades
• Withdrawals, etc.
• Critical. Wallet-drain class UI compromise: any bug enabling malicious transactions with an already-connected wallet (tx parameter substitution, contract address substitution, injected JS/XSS through metadata) or subdomain takeover with wallet interaction
• Critical. Malicious interactions with an already-connected wallet, such as:
• Modifying transaction arguments or parameters
• Substituting contract addresses
• Submitting malicious transactions
• High. Injecting/modifying the static content on the target application (persistent), such as:
• HTML injection without JavaScript
• Replacing existing text with arbitrary text
• Arbitrary file uploads, etc
• XSS
• High. Misrepresentation of transaction data in official explorer/bridge views that can mislead users into loss-inducing actions
• High. Subdomain takeover without already-connected wallet interaction
• High. Taking down the application/website
• Medium. Open redirect

Out of Scope & Rules:

• 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 (governance, strategist) except in such cases where the contracts are intended to have no privileged access to functions that make the attack possible
• 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
• Theoretical impacts without any proof or demonstration
• Impacts involving attacks requiring physical access to the victim device
• Impacts involving attacks requiring access to the local network of the victim
• Reflected plain text injection (e.g. url parameters, path, etc.)
• This does not exclude reflected HTML injection with or without JavaScript
• This does not exclude persistent plain text injection
• Any impacts involving self-XSS
• Captcha bypass using OCR without impact demonstration
• CSRF with no state modifying security impact (e.g. logout CSRF)
• Impacts related to missing HTTP Security Headers (such as X-FRAME-OPTIONS) or cookie security flags (such as “httponly”) without demonstration of impact
• Server-side non-confidential information disclosure, such as IPs, server names, and most stack traces
• Impacts causing only the enumeration or confirmation of the existence of users or tenants
• Impacts caused by vulnerabilities requiring un-prompted, in-app user actions that are not part of the normal app workflows
• Lack of SSL/TLS best practices
• Impacts that only require DDoS
• UX and UI impacts that do not materially disrupt use of the platform
• Impacts primarily caused by browser/plugin defects
• Leakage of non sensitive API keys (e.g. Etherscan, Infura, Alchemy, etc.)
• Any vulnerability exploit requiring browser bugs for exploitation (e.g. CSP bypass)
• SPF/DMARC misconfigured records
• Missing HTTP Headers without demonstrated impact
• Automated scanner reports without demonstrated impact
• UI/UX best practice recommendations
• Non-future-proof NFT rendering
• Blockchain-explorer issues related to the upstream Blockscout issues must be redirected to Blockscout team and their Bug Bounty Program
• Cache poisoning without malicious injection or redirections.

Rewards are distributed according to the impact of the vulnerability based on the HackenProof Vulnerability Classification.

Reward Calculation for Critical Level Reports

For critical web/apps bugs, reports will be rewarded with 25,000 USD, only if the report demonstrates wallet-drain or equivalent financial loss vector.

All other impacts that would be classified as Critical would be rewarded a flat amount of 10,000 USD. The rest of the severity levels are paid out according to the Impact in Scope table.

Reward Payment Terms

Payouts are handled by the Citrea team directly and are denominated in USD. However, payments are done in USDC on Ethereum.

• Critical: 5,000-25,000 USD
• High: 1,000-5,000 USD
• Medium: up to 1,000 USD

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability
• Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
• You must not be a former or current employee of us or one of its contractor.
• ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
• Provide detailed but to-the point reproduction steps
• AI-generated reports without runable PoC are not accepted under this program.

• Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
• No vulnerability disclosure, including partial is allowed for the moment.
• Please do NOT publish/discuss bugs