Our promise to you

• We will aim respond to report in ultimately two weeks!
• We are happy to respond to any questions, please use the button in the right top corner for this.
• We respect the safe harbour clause that you can find below

Your promise to us

• Provide detailed but to-the point reproduction steps
• Include a clear attack scenario. How will this affect us exactly?
• Remember: quality over quantity!
• Reports need to be written
• Please do not discuss or post vulnerabilities without our consent (including PoC's on YouTube and Vimeo)
• Please do not use automatic scanners -be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's 😉)

We're interested to hear about any issue that potentially compromises our applications or its user's security. Before submitting a vulnerability, make sure to check that it's not listed in our out of scope policy (which you can find below). If you have additional questions about our program feel free to contact us through intigriti's support by using the button on the right-hand side (Ask scope question).

Our Wallet UI (wallet) and Wallet API (documentation: wallet) are in scope.

To not force researchers to spend real currency when testing, we have two environments:

1. Production (https://wallet.venly.io and https://api-wallet.venly.io):
   This environment works with real tokens, which have real value.

2. Sandbox (https://wallet-sandbox.venly.io and https://api-wallet-sandbox.venly.io):

   • This environment runs on testnets (e.g. Amoy Testnet for Polygon) in the backend, so the tokens used here do not have any real value.
   • This environment is in a lower tier to encourage you to also try and reproduce any vulnerability found in production

Cross environment

• any vulnerability already discoverd in Sandbox is no longer in scope for Production and visa versa

Sandbox Environment

• Cloudflare Access
• Any vulnerabilities related to infrastructure (e.g. open ports, ...)

Application

• API key disclosure without proven business impact
• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that cannot be used to exploit other users
• Verbose messages/files/directory listings without disclosing any sensitive information
• CORS misconfiguration on non-sensitive endpoints
• Missing cookie flags
• Missing security headers
• Cross-site Request Forgery with no or low impact
• Presence of autocomplete attribute on web forms
• Reverse tabnabbing
• Bypassing rate-limits or the non-existence of rate-limits.
• Best practices violations (password complexity, expiration, re-use, etc.)
• Clickjacking without proven impact/unrealistic user interaction
• CSV Injection
• Sessions not being invalidated (logout, enabling 2FA, etc.)
• Tokens leaked to third parties
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection without being able to modify the HTML
• Username/email enumeration
• Email bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing/Version disclosure
• Not stripping metadata of files
• Same-site scripting
• Subdomain takeover without taking over the subdomain
• Arbitrary file upload without proof of the existence of the uploaded file
• Blind SSRF without proven business impact (pingbacks are not sufficient)
• Disclosed/misconfigured Google Maps API keys
• Host header injection without proven business impact
• Security issues in the blockchain itself

General

• In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
• Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks
• Vulnerabilities that only work on software that no longer receive security updates
• Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
• Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
• Reports that state that software is out of date/vulnerable without a proof-of-concept

Intigriti's contextual CvSS standard is used.

All applications

1. Only create test accounts with your intigriti.me email address and limited to 5 accounts (need more, ask).
2. You can request a clientId for our white-label API via this form (staging) or via the support chat on our website https://venly.io (production)

Market

1. The staging environment is behind Cloudflare Access, you can gain access by using your intigriti.me email address.
2. On our staging environment, you will receive 10 credits when you register, that should be enough for some basic usage.
3. Since we don't have an infinit amount of testnet USDC, please deposit back what you withdraw.
4. If for some scenario you need more credits on staging, you can deposit USDC (on Ropsten test network) or ask more via the support chat.