Memento Blockchain Bug Bounty Program

Program Description

Memento Blockchain (or simply Memento) has one mission: democratizing finance and digital asset management through DeFi products and services.

Security is very important to us and this Bug Bounty program shall help us meet highest industry standards to offer the most secure service and experience to all parties.

Program Rules

• We know that no technology is perfect and that working with skilled security researchers is crucial in identifying weaknesses in our technology.

• If you believe you've found a security bug in our service, we are keen to work with you to resolve the issue promptly and ensure you are fairly rewarded for your discovery.

Testing Policy and Responsible Disclosure

Please adhere to the following rules while performing research on this program:

• Denial of service (DoS) attacks on Memento applications, servers, networks or infrastructure are strictly forbidden.

• Avoid tests that could cause degradation or interruption of our services.

• Do not use automated scanners or tools that generate large amount of network traffic.

• Do not leak, manipulate, or destroy any user data or files in any of our applications/servers.

• Do not copy any files from our applications/servers and disclose them.

• No vulnerability disclosure, full, partial or otherwise, is allowed.

Reward Eligibility

We are happy to thank everyone who submits valid reports which help us improve the security of Memento, 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 (see below).

• The report must contain the following elements:

  • Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and Memento, and remediation advice on fixing the vulnerability

  • Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact

  • Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc

• You must not break any of the testing policy rules listed above

• You must not be a former or current employee of Memento or one of its contractors.

Reward amounts are based on:

• Reward grid of the report's scope

• CVSS scoring and actual business impact of the vulnerability upon performing risk analysis

Reward Grid

Scopes

Memento DFM (Digital Fund Management) dApp

Memento DFM is a multi-chain asset management protocol that allows users to create, mint, and manage ETF-style tokenized funds. You can check our documentation at https://domanifinance.notion.site/DOMANI-DAO-Wiki-eee68e859018473f9e624d711fcbd242.

The dedicated environment to test the Memento DFM dApp (decentralized app) is reachable at https://bug-bounty-dfm.mementoblockchain.com.

It is recommended to use the Metamask wallet when connecting.

Important Notes

• No VPN allowed.

• Use a desktop (the Memento DFM dApp is not mobile friendly).

• No registration is required, just connect your crypto wallet to the Memento DFM dApp (using the testnet blockchains).

• In order to connect to the dApp, you need a crypto wallet like Metamask (https://metamask.io/) or Rabby (https://rabby.io/).

• This is a test environment, pointing to testnet blockchains, and only test tokens (i.e. not real tokens) are required to execute transactions and perform tests.

• In order to execute transactions, you need test tokens in one of these testnets: Ethereum Sepolia, ZKsync Era Sepolia, Avalanche Fuji, Polygon Amoy, Kaia Kairos. The test tokens can be obtained for free from any of the faucets available online.

Out of Scope

• All domains or subdomains not listed in the above list of 'Scopes'.
• Smart contracts.

Qualifying Vulnerabilities

• SQL Injection (SQLi)
• Cross-Site Scripting (XSS)
• Remote Code Execution (RCE)
• Insecure Direct Object Reference (IDOR)
• Horizontal and vertical privilege escalation
• Authentication bypass & broken authentication
• Business Logic Errors vulnerability with real security impact
• Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
• Cross-Origin Resource Sharing (CORS) with real security impact
• Cross-site Request Forgery (CSRF) with real security impact
• Open Redirect

Non-Qualifying Vulnerabilities

• Tabnabbing
• Missing cookie flags
• Content/Text injections
• Mixed content warnings
• Clickjacking/UI redressing
• Denial of Service (DoS) attacks
• Known CVEs without working PoC
• Open ports without real security impact
• Social engineering of staff or contractors
• Presence of autocomplete attribute on web forms
• Vulnerabilities affecting outdated browsers or platforms
• Self-XSS or XSS that cannot be used to impact other users
• Outdated libraries without a demonstrated security impact
• Any hypothetical flaw or best practices without exploitable PoC
• Expired certificate, best practices and other related issues for TLS/SSL certificates
• Unexploitable vulnerabilities (ex: XSS or Open Redirect in HTTP Host Header)
• Reports with attack scenarios requiring MITM or physical access to victim's device
• Missing security-related HTTP headers which do not lead directly to a vulnerability
• Unauthenticated / Logout / Login and other low-severity Cross-Site Request Forgery (CSRF)
• Invalid or missing SPF (Sender Policy Framework), DKIM, DMARC records
• Session expiration policies (no automatic logout, invalidation after a certain time or after a password change)
• Disclosure of information without direct security impact (e.g. stack traces, path disclosure, directory listings, software versions, IP disclosure, 3rd party secrets)
• CSV injection
• HTTP Strict Transport Security Header (HSTS)
• Subdomain takeover without a full working PoC
• Blind SSRF without direct impact (e.g. DNS pingback)
• Lack of rate-limiting, brute-forcing or captcha issues
• User enumeration (email, alias, GUID, phone number)
• Password requirements policies (length / complexity / reuse)
• Ability to spam users (email / SMS / direct messages flooding)
• Disclosed / misconfigured Google API key (including Google Maps)
• Recently disclosed 0-day vulnerabilities (less than 90 days since patch release)
• Password reset token leak on trusted third-party website via Referer header (eg Google Analytics, Facebook…)
• API Authorisation

Hunting Requirements

User Agent

Please append to your user-agent header the following value: -BugBounty-memento-31337.

Temporary Exclusion

We will not be accepting any reports related to API Authorisation for the time being due to a system upgrade.

Hunters Collaboration

When submitting new report, you can add up to 5 collaborators, and define the reward split ratio.

For more information, see the help center at https://helpcenter.yeswehack.io/hunter/hunter-collaboration. Note: For reports that have already been rewarded, it is not possible to redistribute the rewards.