Description

We are happy to announce our Responsible Disclosure program! KU Leuven has a very diverse web landscape. Keeping this environment and the data it contains as secure as possible is an ongoing effort. We would like to invite you to help us with this effort.

Bounties

Responsible disclosure

Rules of engagement
Required
Not applicable
Not allowed
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)
Domains

IPv4: 134.58.0.0/16

No Bounty
IP Range

IPv6: 2a02:2c40::/32

No Bounty
IP Range
In scope

We have done our best to resolve most of our known issues and now would like to request your help to spot the ones we have missed!

We are specifically looking for:

  • leaking of not public personal data
  • horizontal / vertical privilege escalation
  • Application specific vulnerabilities
  • Remote code executions
  • Access to backends (databases,...)
Out of scope

URLs

www.trismegistos.org

Application

  • 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
  • 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 after a credential change
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referer leakage
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Username / email enumeration
  • E-mail 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

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, may be excluded or be lowered in severity
  • Spam, social engineering and physical intrusion
  • DoS/DDoS attacks or brute force attacks.
  • Vulnerabilities that are limited to non-current browsers (older than 3 versions) will not be accepted
  • 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 programs follows Intigriti's contextual CVSS standard.

FAQ

We currently don't offer test credentials for this program.

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
logo
leaderboard
logo
logo
logo
logo
logo
logo
Overall stats
submissions received
573
average payout
N/A
accepted submissions
331
total payouts
N/A
Last 90 day response times
avg. time first response
< 24 hours
avg. time to decide
+3 weeks
avg. time to triage
< 24 hours
Activity
1/26
KU Leuven
closed a submission
1/26
logo
created a submission
1/25
logo
created a submission
1/21
logo
created a submission
1/20
KU Leuven
closed a submission
1/16
KU Leuven
closed a submission
1/16
KU Leuven
closed a submission
1/16
KU Leuven
closed a submission
1/16
KU Leuven
closed a submission
1/16
KU Leuven
accepted a submission