Despite our security efforts a weakness could occur in one of our systems. If you have detected a vulnerability, please let us know. Then we can take the necessary measures as soon as possible, working together with you in an ongoing effort to keep our systems secure.
The Responsible disclosure procedure describes how to report a detected vulnerability.
The network of the University of Twente offers internet access for students, associations and starting companies hosting their websites. Although these sites are on the university's network, they are not the responsibility of the university. Responsible disclosure notifications about these sites are accepted. The reports are forwarded to the responsible persons, but then closed by the university. These reports do not result in an entry in the Hall of Fame and no updates on progress are provided.
A responsible disclosure can be reported using the email address: email@example.com.
Reports need to be clear and contain the steps necessary to reproduce the vulnerability. The steps need to be in the text of the message. Even though images, movies and other files may add to the clarification, they are routinely not opened because of security concerns regarding unsolicited attachments and links.
We want to thank everybody who reported a vulnerability in a responsible way in our Hall of Fame.
Out of scope
The University of Twente does not reward trivial vulnerabilities or bugs that cannot be abused. The following are examples of known and accepted vulnerabilities and risks that are outside the scope of the responsible disclosure policy:
- HTTP 404 codes/pages or other HTTP non-200 codes/pages and Content Spoofing/Text Injection on these pages.
- fingerprint version banner disclosure on common/public services.
- disclosure of known public files or directories or non-sensitive information, (e.g. robots.txt).
- clickjacking and issues only exploitable through clickjacking.
- lack of Secure/HTTPOnly flags on non-sensitive Cookies.
- OPTIONS HTTP method enabled.
- anything related to HTTP security headers, e.g.:
- SSL Configuration Issues:
- SSL forward secrecy not enabled.
- weak / insecure cipher suites.
- SPF, DKIM, DMARC issues.
- host header injection.
- reporting older versions of any software without proof of concept or working exploit.
- information leakage in metadata.