Intigriti
Description

VULNERABILITY DISCLOSURE PROGRAM (VDP) Above all else, University Hospital Zurich is committed to the care and improvement of human life. Part of that mission is to protect our patients, people, systems, and facilities. We want encourage security researchers to feel comfortable reporting vulnerabilities they’ve discovered to us in good faith.

Bounties

This is a responsible disclosure program without bounties.

Rules of engagement
Not applicable
Not applicable
Not applicable
Not applicable

By participating in this program, you agree to:

  • Respect the Community Code of Conduct
  • Respect the Intigriti Terms and Conditions
  • Respect the scope of the program
  • Not discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube and Vimeo)

Validation times

We will validate all submissions within the below timelines, once your submission has been verified by Intigriti.
Submissions validated outside of this may be awarded a €25 bonus.

Vulnerability Severity Time to validate
Exceptional 2 Working days
Critical 2 Working days
High 5 Working days
Medium 15 Working days
Low 15 Working days

This remains at the discretion of Universitätsspital Zürich to award.

Check our fix
We offer up to €50 bonus to verify a resolved issue for us (when requested).
This remains at the discretion of Universitätsspital Zürich to award.

Domains

*.unispital.ch

No bounty
Wildcard

forwarding to usz.ch

*.usz.ch

No bounty
Wildcard

this is our Main Website.
You are welcome to check it all around for security Issues.

In scope

OUR WORST CASE SCENARIOS

  • Medical Devices stop working due to a cyber attack
  • Doctors and Nurses are not able to use the very important lifesaving medical tools to help the Patient
  • Stealing/leaking personal data from our customers (Medical Records etc.)
  • Complete Collapse of our Infrastructure (Servers, Datacenters etc)

YOUR COMMITMENT
You don’t breach any applicable laws in connection with your report and your interaction with USZ Applications or service that lead to your report
You report any vulnerability that you have discovered promptly
You don’t exploit or use in any manner (expet of the purposes to reporting it to USZ), the discovered vulnerabilities
You don’t engage, in testing/research of systems with the intention of harming the University Hospital Zurich, its customers, employees, partners or suppliers
You don’t use, misuse, delete, alter or destroy, any data that you have accessed or may be able to access in relation to the vulnerability
You don’t conduct social engineering, spamming, phishing, denial-of-service or resource-exhaustion attacks
You don’t test the physical security of any property, building, plant or factory of USZ.
You agree not to disclose to any third party any information related to your report, nor the fact that a vulnerability has been reported to USZ.
You agree that you are making your report without any expectation or requirement of reward or other benefit, financial or otherwise.

OUR COMMITMENT
We recognize the value of your contribution and we will use reasonable effort to provide
A timely response to acknowledge the receipt of your report
An open dialog to discuss your vulnerability report
An estimated timeline, where possible, as to when the vulnerability will be fixed

We would like to thank every researcher who submits a vulnerability report and helps us to improve security at University Hospital Zurich.

Out of scope

Application

  • API key disclosure without proven business impact
  • 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 on pages with no sensitive actions
  • CSV Injection
  • Sessions not being invalidated (logout, enabling 2FA, etc.)
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referrer leakage
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection
  • Username/email enumeration
  • Email bombing
  • HTTP Request smuggling without any proven impact
  • Homograph attacks
  • XMLRPC enabled
  • Banner grabbing/Version disclosure
  • Open ports without an accompanying proof-of-concept demonstrating vulnerability
  • Weak SSL configurations and SSL/TLS scan reports
  • Not stripping metadata of images
  • Disclosing API keys without proven impact
  • Same-site scripting
  • Subdomain takeover without taken over the subdomain
  • Arbitrary file upload without proof of the existence of the uploaded file
  • Blind SSRF without proven business impact (DNS pingback only is not sufficient)
  • Disclosed and/or misconfigured Google API key (including maps)
  • Host header injection without proven business impact

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
Severity assessment

This program follows Intigriti's contextual CVSS standard

FAQ

Where can we get credentials for the app?

For the main application, you can self-register on the application but please don’t forget to use your @intigriti.me address.

For other applications that have a self-registration flow, please create your own account using your @intigriti.me email address.

For any applications without a self-registration flow, we currently don’t offer any credentials to test user roles.

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.

Researchers
last contributors
logo
logo
logo
logo
logo
leaderboard
logo
logo
logo
logo
logo
Last 90 day response times
avg. time first response
< 3 days
avg. time to triage
< 3 days
Activity
6/20
Universitätsspital Zürich
closed a submission
6/17
logo
created a submission
5/22
Universitätsspital Zürich
closed a submission
3/12
Universitätsspital Zürich
closed a submission
3/11
logo
created a submission
2/7
Universitätsspital Zürich
changed the out of scope
1/8
Universitätsspital Zürich
accepted a submission
12/19
logo
created a submission
12/11
Universitätsspital Zürich
closed a submission
12/5
logo
created a submission