Finnair Vulnerability Disclosure Program
Finnair looks forward to working with the security community to find vulnerabilities in order to keep our businesses and customers safe.
Gold Standard Safe Harbor
This program adheres to Gold Standard Safe Harbor.
Response Targets
Finnair will make a best effort to meet the following response targets for hackers participating in our program:
| Type of Response | Target in business days |
|---|
| First Response | 2 days |
| Time to Triage | 2 days |
| Time to Resolution | depends on severity and complexity |
We'll try to keep you informed about our progress throughout the process.
Disclosure Policy
- Please do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization.
- Follow HackerOne's disclosure guidelines.
Program Rules
- Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue may not be marked as triaged.
- Submit one vulnerability per report unless you need to chain vulnerabilities to provide impact.
- When duplicates occur, we only triage the first report received (provided that it can be fully reproduced).
- Multiple vulnerabilities caused by one underlying issue will be treated as one valid report.
- Social engineering (e.g. phishing, vishing, smishing) is prohibited.
- Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.
- Only interact with accounts you own or with explicit permission of the account holder.
- Please use your hacker email alias when testing and add headers to requests (such as X-HackerOne-Research: [H1 username]).
Scope
Assets in Scope
- finnair.com and associated web properties (excluding auth.finnair.com)
Out of Scope Assets
- Authentication services (auth.finnair.com domain)
Session Layer: HTTP Headers
Researchers should add headers to requests such as:
- "X-HackerOne-Research: [H1 username]"
Out of Scope Vulnerabilities
When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug. The following issues are considered out of scope:
- Clickjacking on pages with no sensitive actions
- Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
- Attacks requiring MITM or physical access to a user's device
- Previously known vulnerable libraries without a working Proof of Concept
- Comma Separated Values (CSV) injection without demonstrating a vulnerability
- Missing best practices in SSL/TLS configuration
- Any activity that could lead to the disruption of our service (DoS)
- Rate limiting or bruteforce issues on non-authentication endpoints
- Missing best practices in Content Security Policy
- Missing HttpOnly or Secure flags on cookies
- Configuration of or missing security headers
- Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
- Vulnerabilities only affecting users of outdated or unpatched browsers (less than 2 stable versions behind the latest released stable version)
- Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors)
- Tabnabbing
- Issues that require unlikely user interaction
- Improper logout functionality and improper session timeout
- CORS misconfiguration without an exploitation scenario
- Broken link hijacking
- Lack of jailbreak detection in mobile apps
- Lack of SSL Pinning
Leaked Credentials
General Guidelines
- Do not attempt to login with the leaked username/password combination.
- Try to assess the validity based on the domain and the date of the actual leak (not the date of indexing).
- If you are unsure about the validity, create a report for the vulnerability disclosure team to verify the validity of the credentials.
Out of Scope
- Consumer/customer credentials from third-party breach databases or info-stealer logs
- Employee credentials from decommissioned systems or inactive accounts
- Bulk credential dumps without validation of current validity
In Scope
- Valid, current employee credentials from active Finnair systems that pose immediate security risk
Thank you for helping keep Finnair and our users safe!