Bounties
Low
Medium
High
Critical
Exceptional
Tier 2
€ 0
€ 500
€ 1,000
€ 1,500
€ 2,500
Up to € 2,500
Domains

https://webwsp.aps.kuleuven.be/sap/bc/ui5_ui5/sap/zc_oi_appl/

Tier 2
URL

https://associatie.kuleuven.be/inschrijvingen/oli_login_50000050

Tier 2
URL
the registration/login part on idp.kuleuven.be itself is out of scope for the program
Description

The online enrollments application allows students to apply for educational programs at the university or at university colleges. Every year approximately 40.000 applicants enter their personal information and educational preferences into this application. We challenge you to find the bugs in our online enrollment application.

In scope

The scope of this project is the online enrollment application:
https://associatie.kuleuven.be/inschrijvingen/oli_login_50000050

The above link is used to login or create an account. Keep in mind that the registration and login process are considered as out-of-scope. Once logged in, you will proceed to the actual enrollment application. From there, it is in scope.

We are particularly interested in, but not limited to, ways to exploit the tool using:

  • Horizontal or vertical privilege escalation
  • Exploits that facilitate information theft
  • Exploits that facilitate data modification
Out scope

Important!

In order to enroll users must first create an account to enter the application here: https://associatie.kuleuven.be/inschrijvingen/oli_login_50000050

The registration/login part on idp.kuleuven.be itself is out of scope for the program.

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
  • Missing cookie flags on non sensitive cookies
  • Missing security headers which do not present an immediate security vulnerability
  • 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 without sensitive actions
  • CSV Injection
  • Host Header Injection
  • Sessions not being invalidated (logout, enabling 2FA, ..)
  • Hyperlink injection/takeovers
  • Mixed content type issues
  • Cross-domain referer leakage
  • Anything related to email spoofing, SPF, DMARC or DKIM
  • Content injection
  • 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

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 the usage of shared computers, man in the middle or compromised user accounts
  • Recently disclosed zero-day vulnerabilities in commercial products where no patch or a recent patch (< 2 weeks) is available. We need time to patch our systems just like everyone else - please give us 2 weeks before reporting these types of issues.
  • Attacks requiring unrealistic user interaction
Rules of engagement

Types of users

  • Only logged in users can access the Enrollment application. The login is provided by the Identity & Access Management system of KU Leuven.

Guidelines

  • Write your report in Dutch or English.
  • Describe the problem in sufficient detail and include the necessary evidence, such as IP addresses, log entries, screenshots, etc.
  • Provide detailed but to-the-point reproduction steps
  • Include a clear attack scenario; a step by step guide in the PoC is highly appreciated
  • Remember: quality over quantity
  • Only notify the ICTS department of KU Leuven of your findings, and only via this procedure. Do not publish details about the security issue through other channels. Making the problem known through other channels or the media, even before or after notifying the KU Leuven via this procedure and even when not all details are provided, will be considered irresponsible behaviour and can still lead to the filing of criminal charges.
  • Do not exploit the identified leak: only collect the information necessary to demonstrate its existence.
    Handle any found data in a responsible manner: if you can demonstrate that there is a security problem with a small portion, do not go any further
    Please do NOT discuss bugs before they are fixed

Our promise

  • We will response to your report as soon as possible, if you have provided contact information.
  • If we require additional information, we may choose to contact you, if possible.
  • We will do everything possible to solve any shortcomings as quickly as possible, and we will keep you posted.

Safe harbour for researchers

KU Leuven considers ethical hacking activities conducted consistent with the Researcher Guidelines, the Program description and restrictions (the Terms) to constitute “authorized” conduct under criminal law. KU Leuven will not pursue civil action or initiate a complaint for accidental, good faith violations, nor will they file a complaint for circumventing technological measures used by us to protect the scope as part of your ethical hacking activities.

If legal action is initiated by a third party against you and you have complied with the Terms, KU Leuven will take steps to make it known that your actions were conducted in compliance and with our approval.

Severity assessment

It will be the responsibility of intigriti to pay ethical hackers in a timely and legal way. Payouts will only take place after agreement with KU Leuven on the criticality of the impact and only if the submission was the first of its kind and agreed to be valid.

Exceptional

  • Remote code execution
  • Access to the underlying infrastructure

Critical

  • Acquire sensitive data of our users
  • Full database access
  • Vertical privilege escalation
  • Access to all user data or access to a targeted user
  • Data loss

High

  • Access to data of random users
  • Stored cross-site scripting
  • Impersonation of other user (1 user per time)

Medium

  • Reflected cross-site scripting with low or no user interaction
  • Stored cross-site scripting that requires a lot of user interaction
FAQ

How should we create the accounts?

When creating an account, you have to provide first name and last name. First name must be "intigriti" and last name must be "Test". Mailaddress must be your intigriti-mailaddress.

How long does it take to fix a vulnerability?

Our goal is to implement a fix as soon as possible. Depending on the criticality and the affected system it can take up to multiple months to implement a fix.

All aboard!
Please login or register 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 login 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
ID check required
Triage
Activity
10/12
KU Leuven
closed a submission
03/12
KU Leuven
accepted a submission
03/12
KU Leuven
closed a submission
22/11
KU Leuven
closed a submission
22/11
KU Leuven
closed a submission
21/11
KU Leuven
closed a submission
20/11
logo
mehedihasan555552
created a submission
20/11
KU Leuven
closed a submission
20/11
KU Leuven
closed a submission
20/11
KU Leuven
accepted a submission