Voi Vulnerability Disclosure Program

Description

Welcome to Voi's Vulnerability Disclosure Program. At Voi, we're about transforming urban transport. Since 2018, we're on a mission to challenge the car-centric culture and bring in mobility solutions that make city life smoother, greener and more enjoyable.

Bounties

This is a responsible disclosure program without bounties.

Reward policy

While we do not offer bounties for reported vulnerabilities in our VDP, we appreciate your contribution to securing our systems.

If you believe your disclosure may qualify for a reward, please review and submit the report through our bug bounty program.

Rules of Engagement

Required:

• @intigriti.me Required
• User agent Not applicable
• Automated tooling max. 5 requests/sec
• Request header x-intigriti-username: {username}

By participating in this program, you agree to:

• Respect the Community Code of Conduct
• Respect the Intigriti Terms and Conditions
• Respect the scope of the program
• Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Validation time

When you report a potential security vulnerability to us, we commit to:

• Acknowledge receipt of your report within 7 calendar days.
• Provide a status update at least once every 30 calendar days until the vulnerability is resolved or we determine that no further action is required.

Safe harbour for researchers is applied.

Assets

In Scope

All Voi assets - Other - No bounty

Out of Scope

Third-party systems or domains referencing Voi - Other

Scope Details

Introduction

Voi is committed to protecting the security of our users and our products. We welcome vulnerability reports from the security community under our VDP. This program provides researchers with a safe and responsible way to report potential vulnerabilities in Voi systems.

Out of Scope

Researchers must only test systems and services that are owned, operated, or explicitly authorised by Voi. Any systems outside this scope (e.g., third-party systems, vendor services, or partner infrastructure) are out-of-scope and must not be tested.

Excluded Vulnerability Types

Application

• Wordpress usernames disclosure
• Pre-Auth Account takeover/OAuth squatting
• Self-XSS that can't 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 aren't sufficient)
• Disclosed/misconfigured Google Maps API keys
• Host header injection without proven business impact

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

Mobile

• Shared links leaked through the system clipboard
• Any URIs leaked because a malicious app has permission to view URIs opened
• The absence of certificate pinning
• Sensitive data in URLs/request bodies when protected by TLS
• Lack of obfuscation
• Path disclosure in the binary
• Lack of jailbreak & root detection
• Crashes due to malformed URL Schemes
• Lack of binary protection (anti-debugging) controls, mobile SSL pinning
• Snapshot/Pasteboard leakage
• Runtime hacking exploits (exploits only possible in a jailbroken environment)
• API key leakage used for insensitive activities/actions

Severity Assessment

This program follows Intigriti's triage standards based on the proof of concept.

FAQ

Where can we get credentials for the app?

We currently don't offer any credentials to test user roles.

You can self-register on the application but please don't forget to use your @intigriti.me address.