Looking for flight-specific predictions? Sign up for a free trial!
Lumo Vulnerability Disclosure Policy
October 25th, 2020
Lumo is committed to ensuring the confidentiality, availability, and security of our systems and information. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.
This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.
If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and Lumo will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.
Please adhere to the following guidelines during your research:
Notify us as soon as possible after you discover a real or potential security issue.
Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
Do not submit a high volume of low-quality reports.
Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.
The following test methods are not authorized:
Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing), or any other non-technical vulnerability testing
Area of focus
Lumo cares deeply about our customers and their data. Security issues that allow unauthorized access to another user's data (such as passenger PII, trip details, etc.), API keys, passwords, or other data deemed highly sensitive by Lumo are especially of interest, and will be classified as a P0 vulnerability.
We unfortunately do not (yet) have a significant budget for a formal bounty program to compensate researchers. However, we are happy to pay out the following for valid and useful disclosures:
P0: $400 + free lifetime Lumo access
P1: $200 + free lifetime Lumo access
P2: $100 + free lifetime Lumo access
P3 and below: No $ compensation, but free lifetime Lumo access
We are happy to receive vulnerability disclosures on any of our systems at *.thinklumo.com
Of particular interest are the following targets that align with our area of focus:
In order to help us triage and prioritize submissions, we recommend that your reports:
Describe the location the vulnerability was discovered and the potential impact of exploitation.
Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
What you can expect from us
When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.
Within 3 business days, we will acknowledge that your report has been received..
To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
We will maintain an open dialogue to discuss issues.
Questions regarding this policy may be sent to firstname.lastname@example.org. We also invite you to contact us with suggestions for improving this policy.