We've built a brand-new acceptance environment for you to hack on.
New machines, new load-balancer, clean database, you name it...
This environment will receive new features prior to every new production release.

We are interested in any potential vulnerability that could impact the security of the domains listed above.
Examples of issues we'd like to know about :

• Remote Code Execution
• SQL Injection
• File Inclusion / Directory Traversal
• Cross Site Scripting
• Privilege escalation
• Significant enumeration attacks

With rising privacy awareness and regulations like GDPR, we would also like to known how private our data really is. We would like to learn about every vulnerability we are facing:

• Can users see data of other users?
• Can bad guys enter without credentials?
• Can you do what you are not allowed to do?
• What can you break?

Credentials

Test credentials can be requested when logged in by using the request credentials button in the upper right corner of our program's page. Only for the customer login panel (https://aweb.suivo.com) credentials will be given.

Suivo has several permission levels (ranked from low to high):

1. Driver
2. Workshop User
3. Historical Access User
4. Live Access User
5. Power User
6. Full Access User

More information about the permission model can be found HERE

You'll receive the credentials for all roles in the following format:

driver | workshop | historicalaccess | liveaccess | poweruser | fullaccess

With these credentials you are able to test horizontal and vertical privilege escalation.

CSRF - this is a known issue

Application

• 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 on pages with no sensitive actions
• CSV Injection
• Host Header Injection
• Sessions not being invalidated (logout, enabling 2FA, ..)
• Hyperlink injection/takeovers
• Mixed content type issues
• Cross-domain referer leakage
• Anything related to email spoofing, SPF, DMARC or DKIM
• Content injection
• Username / email enumeration
• E-mail bombing
• HTTP Request smuggling without any proven impact
• Homograph attacks
• XMLRPC enabled
• Banner grabbing / Version disclosure
• Open ports without an accompanying proof-of-concept demonstrating vulnerability
• Weak SSL configurations and SSL/TLS scan reports
• Not stripping metadata of images
• Disclosing credentials without proven impact
• Disclosing API keys without proven impact
• Same-site scripting
• Subdomain takeover
• Arbitrary file upload without proof of the existence of the uploaded file

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, may be excluded or be lowered in severity
• Spam, social engineering and physical intrusion
• DoS/DDoS attacks or brute force attacks.
• Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
• Attacks requiring physical access to a victim’s computer/device, man in the middle or compromised user accounts
• Recently disclosed zero-day vulnerabilities in commercial products where no patch or a recent patch (< 2 weeks) is available. We need time to patch our systems just like everyone else - please give us 2 weeks before reporting these types of issues.
• Reports that state that software is out of date/vulnerable without a proof-of-concept

Guidelines

• 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 :-))
• Please do NOT discuss bugs before they are fixed. You can send us a video as proof of concept, but remember to change its privacy settings to private

Reporting Guidelines

• Provide detailed but to-the point reproduction steps
• Include a clear attack scenario. How will this affect us exactly?
• Remember: quality over quantity!

All our rewards are impact based, therefore we kindly ask you to carefully evaluate a vulnerability's impact when picking a severity rating. To give you an idea of what kind of bugs belong in a certain severity rating we've put some examples below. Note that depending on the impact a bug can sometimes be given a higher/lower severity rating.

Exceptional

• Remote code execution
• Full database access
• Gaining access to the underlying infrastructure

Critical

• Acquire sensitive data of our users
• Vertical privilege escalation
• Access to all user data or access to a targeted user

High

• Access to random users their data
• Stored Cross-Site scripting

Medium

• Reflected Cross-Site scripting with no or very little user interaction to trigger
• Stored Cross-Site scripting that require a lot of user interaction

Low

• Clickjacking on static pages or that require unrealistic user interaction

Can we receive test accounts?

Yes, you can fetch a set of credentials by using the "request credentials" button in the upper right corner of our program's page. Only for the customer login panel (https://aweb.suivo.com) credentials will be given.