Intigriti
Description

Swiss Federal Railways - the national railway company of Switzerland. (German: Schweizerische Bundesbahnen, SBB) Welcome to our public Bug Bounty program. We are specifically looking for: * Leaking PII Data (customer) * Data manipulation We will add additional applications/domains to the scope (step by step) to reach our goal. High performance researcher may be invited to our private programs!

Bounties
Low
0.1 - 3.9
Medium
4.0 - 6.9
High
7.0 - 8.9
Critical
9.0 - 9.4
Exceptional
9.5 - 10.0
Tier 1
100
500
750
2,000
5,000
Tier 1
€100 - €5,000
Tier 2
25
125
400
1,000
2,500
Tier 2
€25 - €2,500
Rules of engagement
Required
Not applicable
max. 5 requests/sec
Not applicable

Our promise to you

  • We will respond to reports in ultimately two weeks, probably faster!
  • We are happy to respond to any questions, please use the button in the right top corner for this.
  • We respect the safe harbour clause that you can find below

Your promise to us

  • Provide detailed but to-the point reproduction steps* Include a clear attack scenario. How will this affect us exactly?
  • Remember: quality over quantity!
  • Please do not discuss or post vulnerabilities without our consent (including PoC's on YouTube and Vimeo)
  • Please do not use automatic scanners -be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's 😉)

Conditions of participation

  • SBB employees (including former employees that separated from SBB within the prior 12 months), contingent workers, contractors and their personnel, and consultants are excluded from any payment
  • You may not participate in this program if you are a resident or individual located within a country appearing on any U.S. sanctions lists (such as the lists administered by the US Department of the Treasury’s OFAC).

The researcher guidelines from Intigriti apply in full with the following modifications and additions:

  • SBB reserves the right to change the terms of their Bug Bounty programs at any time and reserves the right to cancel all programs at any time.
  • The relationship between you and SBB is governed by and construed in accordance with the laws of Switzerland. Sole place of jurisdictions are the courts in Bern.
  • You acknowledge and agree that you shall not use your relationship with SBB for any marketing or financing purpose or as reference in any personal or professional presentation, documentation or other material, or in any way utilize (neither on the Internet nor in any other way communicate to the public) any trade name, business name, logotype or trademark of SBB.
Domains

Mobile Apps

Tier 1
Other

SBB Mobile - your personal travel companion for public transport.

SBB Mobile IOS
SBB Mobile Android

SBB Preview - always be among the first to test the latest features.
SBB Preview IOS
SBB Preview Android

Please find more details about the apps in the
FAQ for SBB Mobile and SBB Preview

Tier 1
URL

SwissPass is the key to mobility in Switzerland.

With SwissPass customers can manage their travelcard details easily and use the partner services.

Tier 1
URL
Tier 1
URL

*.sbb.ch

Tier 2
Wildcard

*.sbbmobile.ch

Tier 2
Wildcard

*.swisspass.ch

Tier 2
Wildcard

Mobile Apps

Tier 2
Other

SBB Freesurf - browse the web for free on the train.

SBB Freesurf IOS
SBB Freesurf Android

SBB GO - as a study paricipant, you can record your customer journey with the SBB go app and evaluate SBB Touchpoints along your journey.
SBB GO IOS
SBB GO Android

SBB Inclusive - provides visual and digital customer information in stations and on SBB long-distance services
SBB Inclusive IOS
SBB Inclusive Android

Tier 2
URL
Tier 2
URL
Tier 2
URL
In scope

All domains mentioned in the domains section above.

Out of scope

Out of scope

  • Any domain not listed in the domains section, is out of scope.
  • Some websites (partially) share the same codebase. They can contain common issues so if a specific issue has already been found in another website it will not be accepted e.g., for development, integration and production environments.

General

  • In case that a reported vulnerability was already known to the company from their own tests, it will be flagged as a duplicate
  • Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks
  • Vulnerabilities that only work on software that no longer receive security updates
  • Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
  • Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation may be reported, but are usually not eligible for a bounty
  • Reports that state that software is out of date/vulnerable without a proof-of-concept

Application

  • API key disclosure without proven business impact
  • Wordpress usernames disclosure
  • Pre-Auth Account takeover/OAuth squatting
  • Self-XSS that cannot be used to exploit other users
  • Verbose messages/files/directory listings without disclosing any sensitive information
  • CORS misconfiguration on non-sensitive endpoints
  • Missing cookie flags
  • Missing security headers
  • Cross-site Request Forgery with no or low impact
  • Presence of autocomplete attribute on web forms
  • Reverse tabnabbing
  • Bypassing rate-limits or the non-existence of rate-limits.
  • Best practices violations (password complexity, expiration, re-use, etc.)
  • Clickjacking without proven impact/unrealistic user interaction
  • CSV Injection
  • Sessions not being invalidated (logout, enabling 2FA, etc.)
  • Tokens leaked to third parties
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection without being able to modify the HTML
  • Username/email enumeration
  • Email bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing/Version disclosure
  • Not stripping metadata of files
  • Same-site scripting
  • Subdomain takeover without taking over the subdomain
  • Arbitrary file upload without proof of the existence of the uploaded file
  • Blind SSRF without proven business impact (pingbacks are not sufficient)
  • Disclosed/misconfigured Google Maps API keys
  • Host header injection without proven business impact

Mobile Apps

  • Shared links leaked through the system clipboard
  • Any URIs leaked because a malicious app has permission to view URIs opened
  • The absence of certificate pinning
  • Sensitive data in URLs/request bodies when protected by TLS
  • Lack of obfuscation
  • Path disclosure in the binary
  • Lack of jailbreak & root detection
  • Crashes due to malformed URL Schemes
  • Lack of binary protection (anti-debugging) controls, mobile SSL pinning
  • Snapshot/Pasteboard leakage
  • Runtime hacking exploits (exploits only possible in a jailbroken environment)
  • API key leakage used for insensitive activities/actions
Severity assessment

To reward your efforts we are using Intigriti's Contextual CVSS.

FAQ

How do I get credentials?

For applications in our public program, we do not provide any credentials, please feel free to register yourself where possible (with your intigriti.me email address).
Exception: Existing SwissPass users may use their personal accounts on their own risks.

All aboard!
Please log in or sign up on the platform

For obvious reasons we can only allow submissions or applications for our program with a valid Intigriti account.

It will only take 2 minutes to create a new one or even less to log in with an existing account, so don't hesitate and let's get started. We would be thrilled to have you as part of our community.

Program specifics
no reputation No collaboration
Researchers
last contributors
logo
logo
logo
logo
logo
logo
leaderboard
logo
logo
logo
logo
logo
logo
Last 90 day response times
avg. time first response
< 2 days
avg. time to decide
< 2 weeks
avg. time to triage
< 3 days
Activity
7/23
SBB
closed a submission
7/22
SBB
accepted a submission
7/22
logo
created a submission
7/18
SBB
closed a submission
7/18
SBB
closed a submission
7/17
logo
created a submission
7/16
logo
created a submission
7/15
SBB
accepted a submission
7/15
SBB
accepted a submission
7/15
SBB
closed a submission