Vulnerability Disclosure Program
This Vulnerability Disclosure Program was last updated on August, 2019.
Committed to Coordination
If you have information related to security vulnerabilities of Float Mobility products or services, we want to hear from you. Please submit a report in accordance with the guidelines below. We value the positive impact of your work and thank you in advance for your contribution.
Float Mobility agrees to not pursue civil claims against researchers related to the disclosures submitted through this website who:
- do not cause harm to Float Mobility, our customers, or others;
- provide a detailed summary of the vulnerability, including the target, steps, tools, and artifacts used during discovery (the detailed summary will allow us to reproduce the vulnerability);
- do not compromise the privacy or safety of our customers and the operation of our services. Specifically
- contact us immediately if you inadvertently encounter user data;
- do not view, alter, save, store, transfer, or otherwise access the data, and immediately purge any local information upon reporting the vulnerability to Float Mobility;
- act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services (including denial of service);
- comply with all applicable laws;
- do not violate any other law (other than those that would result only in claims by Float Mobility), or disrupt or compromise any data or vehicle that is not their own;
- publicly disclose vulnerability details only after Float Mobility confirms completed remediation of the vulnerability and not publicly disclose vulnerability details if there is no completion date or completion cannot be ascertained;
- confirm that they are not currently located in or otherwise ordinarily resident in Cuba, Iran, North Korea, Sudan, Syria or Crimea; and
- confirm that they are not on the U.S. Department of the Treasury's Specially Designated Nationals List.
Out of Scope
- Reports from automated tools or scans
- Issues without clearly identified security impact (such as clickjacking on a static website), missing security headers, or descriptive error messages
- Missing best practices, information disclosures, use of a known-vulnerable libraries or descriptive / verbose / unique error pages (without substantive information indicating exploitability)
- Speculative reports about theoretical damage without concrete evidence or some substantive information indicating exploitability
- Forms missing CSRF tokens without evidence of the actual CSRF vulnerability
- Self-exploitation (e.g., cookie reuse)
- Reports of insecure SSL / TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner such as SSL Labs)
- Our policies on presence/absence of SPF / DMARC records
- Password complexity requirements, account/e-mail enumeration, or any report that discusses how you can learn whether a given username or email address has a Float Mobility-related account
- Missing security-related HTTP headers which do not lead directly to a vulnerability
- Self Cross-site Scripting vulnerabilities without evidence on how the vulnerability can be used to attack another user
- Social engineering of Float Mobility employees or contractors
- Any physical attempt against Float Mobility property or data centers
- Presence of autocomplete attribute on web forms
- Missing secure cookie flags on non-sensitive cookies
- Denial of Service Attacks
- Banner identification issues (e.g., identifying what web server version is used)
- Open ports which do not lead directly to a vulnerability
- Open redirect vulnerabilities
- Publicly accessible login panels
- Content spoofing / text injection
Float Mobility agrees not to pursue civil action against researchers who comply with Float Mobility's policies regarding this vulnerability disclosure program. We consider activities conducted consistent with the Float Mobility Policy Terms to constitute "authorized" conduct under the Computer Fraud and Abuse Act. Also, if you comply with the Float Mobility Policy Terms, we will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.
If legal action is initiated by a third party against you and you have complied with the Float Mobility Policy Terms, we will, if asked, state that your actions were conducted in compliance with this policy.
You may contact us as follows: firstname.lastname@example.org