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 in hearing about any issue that could potentially compromise our applications or our users' security. Before submitting a vulnerability, please 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 "Ask Scope Question" button on the right-hand side.

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

How to Get API Access?

Credentials to access our APIs can be obtained by registering on our Portal. This provides you with a 14-day free trial, no questions asked. The trial grants access to all our APIs in both Production and Sandbox environments.

Once you've signed up, follow our documentation on how to authenticate.

Funds

To ensure researchers don’t need to spend real currency while testing, we offer two environments:

1. Production

• URLs: wallet.venly.io and api-wallet.venly.io
• This environment works with real tokens, which have real value.

2. Sandbox

• URLs: wallet-sandbox.venly.io and api-wallet-sandbox.venly.io
• This environment runs on testnets (e.g., Amoy Testnet for Polygon), so the tokens used here do not have real value.
• We provide a Faucet in our Portal, which you can use to obtain testnet tokens.
• It's in a lower tier, encouraging you to try and reproduce any vulnerabilities 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
• Cross site scripting vulnarabilities on swagger UI endpoints

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.

Wallet UI

Only create test accounts using your @intigriti.me email address. You can create up to five accounts, if you need more, please ask.

Wallet API

How do I get access to the API?

You can register on our Portal, which provides a 14-day free trial account, no questions asked. This trial grants access to all our APIs in both our Production and Sandbox environments.

Once you've signed up, follow our documentation on how to authenticate.

What if I need more than 14 days?

You can request an extension via the customer support widget in our Portal.

Note: Trial extensions are only available for @intigriti.me email addresses.

I previously used the trial, but I want to access the API again. How can I regain access?

If your 14-day trial has expired and you need access again, you can request a new trial via the customer support widget in our Portal.

Note: New trials are only available for @intigriti.me email addresses.

Where can I get testnet funds for my research?

We provide a Faucet in our Portal, which you can use to obtain testnet tokens.