
JetBlue
External Program
Submit bugs directly to this organization
JetBlue is committed to protecting the security of our systems and our customer's information. To meet our goals, we encourage and support ethical security researchers in reporting vulnerabilities they’ve discovered, in accordance with this Vulnerability Disclosure Policy.
This policy describes what systems and types of research are covered under this policy and how to send us vulnerability reports. By submitting information about a potential vulnerability, you agree to this Policy.
Any services not expressly listed in the Scope section, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in JetBlue systems from our business partners fall outside of this policy’s scope and should be reported directly to the business partner according to their disclosure policy (if any).
The following test types are not authorized:
If you encounter any of the below on our systems while testing within the scope of this policy, stop your testing and report it to the program immediately:
If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, and will work with you to understand and resolve the issue quickly.
Reports should include:
Please keep your vulnerability reports current by updating your report with any new information as it becomes available. We may share your vulnerability reports with any affected business partners.
At JetBlue, we believe that public disclosure of vulnerabilities is an essential part of the vulnerability disclosure process, and that one of the best ways to make software better is to enable everyone to learn from each other’s mistakes.
At the same time, we believe that disclosure in absence of a readily available patch tends to increase risk rather than reduce it, and so we ask that you refrain from sharing your report with others while we work on our patch. If you believe there are others that should be informed of your report before the patch is available, please let us know so we can make arrangements.
We may want to coordinate an advisory with you to be published simultaneously with the patch, but you are also welcome to self-disclose if you prefer. By default, we prefer to disclose everything, but we will never publish information about you or our communications with you without your permission. In some cases, we may also have some sensitive information that should be redacted, and so please check with us before self-disclosing.