Description

Tempo-Team offers daily new and varied jobs for every level and field.

Bounties

Responsible disclosure

Domains

*.tempo-team.*

No Bounty
URL

Any related Tempo-Team domain

No Bounty
URL

www.tempo-team.be

No Bounty
URL
🇳🇱🇫🇷

www.tempo-team.com

No Bounty
URL
🇩🇪

www.tempo-team.nl

No Bounty
URL
🇳🇱
In scope

We are happy to announce our responsible 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 personal data
  • horizontal / vertical privilege escalation
  • SQLi
  • ...
Out of scope

The use of automated scanners on forms is STRICTLY PROHIBITED!

Endpoints

Any endpoints which are not own by Tempo-Team are out of scope, as for example :

  • Company alliance
  • Third parties systems are out of scope

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
  • Subdomain takeover without taking over the subdomain
  • Arbitrary file upload without proof of existence of the uploaded file
  • public API keys without proven 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, 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

Our promise to you

  • We are happy to respond to any questions, please use the button in the right top corner for this.
  • We respect the safe harbour clause that you can find below

Your promise to us

  • Provide detailed but to-the point reproduction steps
  • Include a clear attack scenario. How will this affect us exactly?
  • Remember: quality over quantity!
  • Please do not discuss or post vulnerabilities without our consent (including PoC's on YouTube and Vimeo)
  • Please do not use automatic scanners -be creative and do it yourself! We cannot accept any submissions found by using automatic scanners. Scanners also won't improve your skills, and can cause a high server load (we'd like to put our time in thanking researchers rather than blocking their IP's 😉)

Safe harbour for researchers

Randstad considers ethical hacking activities conducted consistent with the Researcher Guidelines, the Program description and restrictions (the Terms) to constitute “authorized” conduct under criminal law. Randstad 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, Randstad will take steps to make it known that your actions were conducted in compliance and with our approval.

Severity assessment

Exceptional

  • RCE (Remote Code Execution)

Critical

  • Access to all customer 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
FAQ

Where can we get credentials for the app?

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

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.

Program specifics
ID check required
Reputation points
Triage
Overall stats
submissions received
55
average payout
N/A
accepted submissions
23
total payouts
€950
Last 90 day response times
avg. days first response
0.58
avg. days to decide
16.89
avg. days to triage
1.00
Activity
9/29
Randstad
has suspended the program
9/15
Randstad
accepted a submission
9/15
Randstad
closed a submission
9/15
Randstad
accepted a submission
9/15
Randstad
accepted a submission
9/14
Randstad
closed a submission
9/12
logo
papyrus
created a submission
9/11
logo
codecoder
created a submission
9/10
Randstad
closed a submission
9/8
Randstad
closed a submission