Description

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

Bounties

Responsible disclosure

Rules of engagement
Required
Not applicable
max. 5 requests/sec
Not applicable

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 😉)
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
  • ...

⛔️ The use of automated scanners on forms is STRICTLY PROHIBITED! ⛔️

Out of scope

Domains

*.tempo-team.de

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

  • Pre-auth account takeover / oauth squatting
  • 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
  • Missing security headers
  • 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
  • Blind SSRF without proven business impact (DNS pingback only is not sufficient)
  • Disclosed and/or misconfigured Google API key (including maps)
  • Host header injection without proven business impact
  • 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
  • Disclosing credentials without proven impact
  • 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

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.

Researchers
last contributors
logo
logo
logo
logo
logo
logo
leaderboard
logo
logo
logo
logo
logo
logo
Overall stats
submissions received
116
average payout
N/A
accepted submissions
37
total payouts
N/A
Last 90 day response times
avg. time first response
< 24 hours
avg. time to decide
< 2 days
avg. time to triage
< 2 days
Activity
2/24
logo
created a submission
2/22
Randstad
closed a submission
2/20
Randstad
accepted a submission
2/20
Randstad
closed a submission
2/19
logo
created a submission
2/19
logo
created a submission
1/31
Randstad
closed a submission
1/25
Randstad
closed a submission
1/24
logo
created a submission
11/16
Randstad
closed a submission