Lista DAO
Lista DAO, powered by the BNB Smart Chain, introduces an innovative integration of Liquid Staking and Staking services. Lista DAO's native CDP stablecoin is known as lisUSD, and it is over-collateralized against a variety of tokens such as BNB, ETH, wBETH and slisBNB.
PoC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
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
Taking down the application/website
Direct theft of user funds
Execute arbitrary system commands
Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)
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.
Subdomain takeover with already-connected wallet interaction
Malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions
Theft of unclaimed yield
Out of scope
Websites
- Content spoofing / Text injection issues without any security impact
- Server-side information disclosure such as IPs, server names, and most stack traces
- Vulnerabilities used to enumerate or confirm the existence of users or tenants
- Vulnerabilities requiring unlikely user actions or complex user interactions
- URL Redirects (unless combined with another vulnerability to produce a more severe impact)
- Attacks requiring privileged access from within the organization
- Feature requests or suggestions for best practices
- Internal SSRF (Server-Side Request Forgery)
- Path Traversal without real security impact
- Clickjacking without sensitive actions
- Issues related to browser-specific behavior that do not pose a security threat
- Denial of Service (DoS) attacks not explicitly allowed in scope
- Vulnerabilities in third-party software or libraries without evidence of impact on our service
- Issues with non-production environments (staging, testing, etc.)
XSS reports are restricted to those that have an impact of prompting a user to sign a transaction or a redirect.
Backend Services
- Missing or misconfigured security headers that do not lead to direct security vulnerabilities
- Information disclosure of non-sensitive data (e.g., stack traces, debug messages)
- Issues related to outdated software versions unless they can be exploited in our context
- Rate-limiting or brute-force attacks on non-critical endpoints
- Vulnerabilities requiring extensive social engineering or phishing
- Any issues that require physical access to our servers or network
- Findings from automated scans without a proof of concept demonstrating security impact
- Low-impact vulnerabilities that require unlikely attack scenarios
- Directory listing on non-sensitive directories
- Server configuration issues without a clear security impact
- Cosmetic issues and text errors
Smart Contract specific
- Incorrect data supplied by third party oracles
- Not to exclude oracle manipulation/flash loan attacks
- Impacts requiring basic economic and governance attacks (e.g. 51% attack)
- Lack of liquidity impacts
- Impacts from Sybil attacks
- Impacts involving centralization risks
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