Full Disclosure Security Policy
Urban Airship’s security policy provides guidelines for interaction between our company and security researchers. Upon discovering a security issue and communicating it with email@example.com, a researcher can expect a response within five business days. If a researcher does not receive correspondence from someone at Urban Airship within those five business days, they’re entitled to publicly disclose the security problem. However, we’d much prefer to work on fixing the security problem before the public disclosure.
Urban Airship is responsible for delivering status updates at least once every five business days until the problem is resolved or a fix is scheduled for release. We ask for full participation from researchers during this period.
Urban Airship issues related to email spoofing (SPF / DKIM), TLS ciphers, and web server headers are, for the time being, out of scope.
Our aim is to provide the best services we can in a highly secure fashion. We take security very seriously. Part of that is communication with the security community at large. We are providing this policy as a way to get in touch with us when researchers spot issues within our system. This gives researchers a way to give us feedback and to act as a guide for communication between the researcher and Urban Airship.
Working with Urban Airship is, of course, a voluntary choice, and a choice that hopefully researchers respect and accept accordingly. The goal of following this policy, above all else, is education: for Urban Airship, for the researcher, our customers, and the community.
In Scope Security Vulnerabilities
|Injection||Acknowledgement + T-Shirt||SQL Injection, permanent data changes|
|Broken Authentication||Acknowledgement + T-Shirt||Session hijacking, improper logout, authentication replay|
|Cross-Site Scripting (XSS)||Acknowledgement||Unexpected alert boxes, forced IFrame loads|
|Insecure Direct Object References||Acknowledgement + T-Shirt||Bypassing standard user access controls to produce more data than is allowed by current user|
|Security Misconfiguration||Acknowledgement + T-Shirt||Basic security configurations missing, allowing improper information disclosure|
|Sensitive Data Exposure||Acknowledgement + T-Shirt||Fundamental encryption in place is bypassed allowing data disclosure|
|Missing Function Level Access Control||Acknowledgement + T-Shirt||Accessing privileged resources directly without user access control rules being applied|
|Cross-Site Request Forgery (CSRF)||Acknowledgement + T-Shirt||Allowing state changing behavior without a secret token|
|Invalidated Redirects and Forwards||Acknowledgement + T-Shirt||Allowing redirection to another URL without first validating the intended target|
|Remote Code Execution (RCE)||Case by Case basis||Allowing direct access to underlying Operating System or Database with privileged Access|
Out of Scope Vulnerabilities
|Denial of Service||NONE||Any action that disables or makes Urban Airship resources unavailable|
|Distributed Denial of Service||NONE||Performance testing, maxing out network bandwidth, or overloading resources with multiple sources|
|Brute Force Attacks||NONE||Persistent or iterative attacks against Urban Airship production environments|
|Using components with Known Vulnerabilities||NONE||Reporting 3rd party components or libraries Urban Airship is currently using are out of date or vulnerable|
|Bulk Export of Data||NONE||Removing data from Urban Airship without our permission in bulk from our systems.|
|Non-Disclosure of Security Bug||NONE||No bounty or acknowledgement will be issued for disclosing a bug or vulnerability publicly without informing Urban Airship in accordance with this policy|
This hypothetical workflow illustrates the simple set of guidelines at work behind this policy:
- Researcher discovers a security threat
- Researcher documents the threat
- Researcher sends email to firstname.lastname@example.org with the details of the security issue
- Within five days, Urban Airship will responds to researcher with status regarding security issue and possible resolutions
- Every five days thereafter, Urban Airship is required to send a status update to the researcher, and to seek feedback on solutions
- When security issue has been satisfactorily resolved, researcher is welcome to publicly disclose finding
To send secure emails to our security team, please use the following PGP Fingerprint:
This is an open-ended dialogue. If there is anything missing, or if you’re just curious, please send us an email at email@example.com.
Hall of Fame
The hall of fame recognizes researchers findings publicly for the last four quarters. Thank you to everyone for your submissions and for working closely with Urban Airship.
|Ashishkumar Dhaduk||India||Q3 FY'15||XSS||2015/07/06|
|Ashish Pathak||India||Q2 FY'15||Misconfigured SPF||2015/06/16|
|Abrar Afridi||Pakistan||Q2 FY'15||CSRF||2015/04/01|
|Sumit Sahoo||India||Q4 FY'15||Session Management||2015/09/01|
|Rui Silva||Portugal||Q4 FY'15||Redirection||2015/09/01|