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.

This remains at the discretion of RGF Staffing Belgium 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 RGF Staffing Belgium to award.

Rewards
We do not offer monetary rewards for Responsible Disclosure reports, but if you report via our RGF Staffing Responsible Disclosure program on Intigriti, for all valid Medium+ reports we do offer swag as a sign of appreciation.
‍
The only monetary reward exceptions are the specific assets listed in our Registered Bug Bounty Program on Intigriti. Please note that for the Registered Bug Bounty Program, we will only accept reports for those assets that are listed into the program scope and no other variations.
For all other assets, regardless of the reporting method, we recognize researchers who submit previously unknown vulnerabilities that result in a code or configuration change by offering a place in our Security Hall of Fame (HoF).

Duplicates
When duplicates occur, we will only accept the first report. A duplicate is a vulnerability that we are already aware of, regardless of how we first became aware of it (it could have also been discovered by us internally).

Disclosure
You are not allowed to publicly discuss or publish any vulnerability before it has been fixed and you have received explicit permission from us to do so.

Introduction

We are happy to announce our Responsible Vulnerability Disclosure Program!

We've done our best to clean most of our known issues and now would like to request your help to spot the once we missed! We are specifically looking for:

• Leaking of PII data (personal data)
• Horizontal / Vertical privilege escalation
• Information leaks of other candidates or customers/clients.
• Access to information and/or documents of other candidates or customers/clients.
  ...

Shared codebase disclaimer
Websites may partially share the same codebase across multiple domains. They can contain common issues. If a specific issue has already been found in another website, it will be treated as a duplicate.

Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here:
Program Feedback Link
Please note this form will be checked periodically and should not be used for submission or support queries.

Note
Important note: Please remove uploaded testfiles after you're done!

Application

• Anything related to email spoofing, SPF, DMARC or DKIM
• API key disclosure without proven business impact
• Arbitrary file upload without proof of the existence of the uploaded file
• Banner grabbing/Version disclosure
• Best practices violations (password complexity, expiration, re-use, etc.)
• Blind SSRF without proven business impact (pingbacks are not sufficient)
• Bypassing rate-limits or the non-existence of rate-limits.
• Clickjacking without proven impact/unrealistic user interaction
• Content injection without being able to modify the HTML
• CORS misconfiguration on non-sensitive endpoints
• Cross-site Request Forgery with no or low impact
• CSV Injection
• Disclosed/misconfigured Google Maps API keys
• Email bombing
• Homograph attacks
• Host header injection without proven business impact
• HTTP Request smuggling without any proven impact
• IDOR findings are currently out of scope on pen-app.entrili.com
• Improper Input Validation
• Missing cookie flags
• Missing security headers
• Missing CSP headers
• Not stripping metadata of files
• Pre-Auth Account takeover/OAuth squatting
• Presence of autocomplete attribute on web forms
• Reverse tabnabbing
• Same-site scripting
• Self-XSS that cannot be used to exploit other users
• Sessions not being invalidated (logout, enabling 2FA, etc.)
• Subdomain takeover without taking over the subdomain
• Tokens leaked to third parties
• Updates/Deletes/Inserts that are followed by a http 202 OK (as some requests are done in an asynchronious way).
• Validation is performed by back-end systems and not visible to users.
• Username/email enumeration
• Verbose messages/files/directory listings without disclosing any sensitive information
• Wordpress usernames disclosure
• XMLRPC enabled
• XSS cache poisoning / X-Forwarded-Prefix+ & Stored Cross-Site Scripting

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

Mobile

• Shared links leaked through the system clipboard
• Any URIs leaked because a malicious app has permission to view URIs opened
• The absence of certificate pinning
• Sensitive data in URLs/request bodies when protected by TLS
• Lack of obfuscation
• Path disclosure in the binary
• Lack of jailbreak & root detection
• Crashes due to malformed URL Schemes
• Lack of binary protection (anti-debugging) controls, mobile SSL pinning
• Snapshot/Pasteboard leakage
• Runtime hacking exploits (exploits only possible in a jailbroken environment)
• API key leakage used for insensitive activities/actions

This program follows Intigriti's contextual CVSS standard

related to leakage of PII, this will most likely always result in Critical or Exceptional

Exceptional

• RCE (Remote Code Execution)
• Access to all customer/candidate personal data

Critical

• Access to other customers/candidate's personal data
• SQL injection

High

• Stored XSS without user interaction
• Privilege escalation
• Authentication bypass on critical infrastructure

Medium

• XSS
• CSRF with a significant impact

Low

• XSS that requires lots of user interaction ( > 3 steps)
• CSRF with a very limited impact

Where can we get credentials for the app? (https://uat-www.startpeople.be, https://uat-www.unique.be ,...)

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

Where can we get credentials for the app? (https://uat-www.brightplus.be)

You can self-register on the application but please don’t forget to use your @intigriti.me address.
To access the site, there is a pre-authentication

• username: brightplus
• password: uechiegun7usieyoo

Is the platform accessible 24/7?

Yes, however, please note that there are functional/content releases every monday, wednesday & friday between 11-12AM Belgium time

Mails are not arriving

Mails will be only sent on this UAT environment in the user creation part. When using functionality to apply for a job etc, no mails will be sent.