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!

You will be hacking into our staging environment.
This environment runs a copy of our production code, but will receive new features a couple of week in advance of their release to production.

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?

Access Control

Suivo utilises a fairly complex access control system consisting of profiles containing a collection of granted permissions.
To facilitate your understanding, user accounts based on 2 of these profiles will be provided.

• Full Access -> high privilege, can view and edit anything except user management
• Driver -> low privilige, very limited subset of permissions

A detailed comparison between these 2 profiles can be found in the attached Permission Matrix. ('x' marks a granted permission)

Some remarks to keep in mind while attempting privilege escalation:

• Our basic entities (Unit, Person, Location) are visible throughout the application and by every profile
• A User is not equal to a Person. Users are logins, Persons are people who can drive around in Vehicles.
• Users are only visible to the Admin

Customers

Suivo is a SAAS platform hosting data for a variety of Customers.
The last thing we want to happen is Customer A being able to view or manipulate data from Customer B.
To facilitate testing vulnerabilities leading to this scenario, we've create a second Customer account 'Intigriti2' for you to test on.
Please keep this second Customer a clean environment and use it only to verify your actions excuted by Users linked to 'Intigriti1'.

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.

CSRF - this is a known issue

Application

• 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 on pages with no sensitive actions
• CSV Injection
• Blind SSRF without proven business impact (DNS pingback only is not sufficient)
• Disclosed and/or misconfigured Google API key (including maps)
• Host header injection without proven business impact
• 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 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

This program follows Intigriti's contextual CVSS standard

Business impact will be based on the reach of the attack.
Vulnerabilities affecting only a single Customer will have a lower impact, while those affecting multiple Customers will be considered high impact.

Can we receive test accounts?

Only credentials for the customer login panel (https://aweb.suivo.com) will be given. You can create your own account by

1. Logging in to the account manager (shared account - do not test on this!) (credentials below)
2. Going to Admin (top right) → Users (dropdown)
3. Clicking 'Create new'
4. Filling in your details
   • Use your @intigriti.me email address
   • As your role (under User Profile → Profile dropdown), pick either 'Full Access' or 'Driver' (this role has the lowest permissions)
5. At the bottom of this modal, for 'Authentication' the options are
   • Use email as login → preferred
   • Use third-party login → okay to test
   • Username / password → deprecated, please don't focus on testing this flow
6. Clicking create

Login credentials for the account manager are Intigriti1UserManager1:ybz*cvt4cah_fxw4DEZ, but do not test with this account, only use it to create your own account as described above.