OneDoc

Important

⚠️⚠️ Using a real doctor for your test is strictly forbidden ⚠️⚠️

Please use the fake doctor - Dr Bug Bounty to do your tests.

About

Welcome to the OneDoc Bug Bounty program! We're excited to offer a way for the security community to help us find and fix vulnerabilities on our platform.

Our mission, as a leading healthcare service provider in Switzerland, is to ensure the confidentiality, integrity, and availability of our users' (patients and healthcare professionals) data.

We believe that no technology is perfect and that working with skilled security researchers is crucial in identifying weaknesses in our technology.
If you've found a security bug in our service, we are happy to work with you to resolve the issue promptly and ensure you are fairly rewarded for your discovery.

Program Rules

We ask that you conduct your bug bounty activities in a way that does not impact the experience of our platform. If you are interested in testing something that may be considered dangerous, please contact us through the Yes We Hack platform to provide the necessary testing conditions.

Testing Policy and Responsible Disclosure

Please adhere to the following rules while performing research on this program:

• Denial of service (DoS) attacks on our applications, servers, networks or infrastructure are strictly forbidden.
• Do not perform tests that could cause degradation or interruption of our services.
• Avoid using automated tools, or use them the gentle way (max 5 requests per second).
• Do not leak, manipulate, or destroy any user data or files in any of our applications/servers.
• Do not copy any files from our applications/servers and disclose them.
• No vulnerability disclosure, full, partial or otherwise, is allowed.
• All testing made under the OneDoc Bug Bounty program must not have any negative impact on the care team or patients, in accordance with the “Hunting Requirements” below.
• Only trigger notifications targeting email addresses and phone numbers you own and do not trigger large amounts (>30) of notifications (sms/emails).

Reports of leaks and exposed credentials

In the context of this program, we do not intend to encourage, accept or reward reports of leaks that are not applicable to our program’s scope and identified outside of our program’s scope, such as:

• Exposed credentials in/from an out-of-scope asset/source
• Sensitive information exposed in/from an out-of-scope asset/source

Also, in order not to encourage dark and grey economies, in particular the purchase, resale and trade of identifiers or stolen information, as well as all types of dangerous behavior (e.g. social engineering, ...), we will not accept or reward any report based on information whose source is not the result of failure on the part of our organization or one of our employees/service providers.

This excludes, but is not limited to:

• Stolen credentials gathered from unidentified sources (e.g. …)
• Exposed credentials that are not applicable on the program’s scope
• Exposed GitHub/GitLab (or similar) instance with no direct relation with our program’s scope
• Exposed secrets (e.g. API tokens/keys or other technical credentials) that are not directly related to the program’s scope
• Exposed PII on an out-of-scope asset

To summarize our policy, you may refer to this table :

Important precautions and limitations

As a complement to the Program’s rules and testing policy :

• DO NOT alter compromised accounts by creating, deleting or modifying any data
• DO NOT use compromised accounts to search for post-auth vulnerabilities (they won’t be eligible anyway)
• DO NOT include Personally Identifiable Information (PII) in your report and please REDACT/OBFUSCATE the PII that is part of your PoC (screenshot, server response, JSON file, etc.) as much as possible.
• In case of exposed credentials or secrets, limit yourself to verifying the credentials validity
• In case of sensitivie information leak, DO NOT extract/copy every document or data that is exposed and limit yourself to describe and list what is exposed.

Reward Eligibility

We are happy to thank everyone who submits valid reports which help us improve the security of OneDoc, however only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability (see below).
• The report must contain the following elements:
  • Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and OneDoc, and remediation advice on fixing the vulnerability
  • Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact
  • Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc.
• You must not break any of the testing policy rules listed above
• You must not be a former or current employee of OneDoc or one of its contractors.

Reward amounts are based on:

• Reward grid of the report's scope
• CVSS scoring and actual business impact of the vulnerability upon performing risk analysis

Complements about our scopes

onedoc.ch

Our public application, which allows patients to:

• Look for a healthcare professional
• View the profile of a healthcare professional
• Book and manage appointments with a healthcare professional
• Create an account on OneDoc (at the time of the booking)

telehealth.onedoc.ch

Our video consultation application, accessible through a link sent to the patient by email so they can remotely consult their doctor. Patients should not be able to access a video room that is not created for them.

pro.onedoc.ch

Our professional application, only accessible to registered and verified healthcare professionals. Patients should not be able to login.