Description

Red Bull appreciates the work of security researchers to make the internet a better - and more secure - place. Even though we aim to prevent security issues by applying state-of-the art development and operations processes, systems and technical services outside our direct control might have vulnerabilities and weaknesses and we aim to identify and address those before any negative impact occurs. As appreciation we have a unique reward system in place, please see FAQ for more information.

Bounties

Responsible disclosure

Domains

*.redbull.com

No Bounty
URL

*.redbullmediahouse.com

No Bounty
URL

~ 2300 other domains, if it is confirmed to be Red Bull related asset then it's in scope

No Bounty
Other
Easy way to verify if a domain belongs to Red Bull is to have a look-up on the whois record. Information you need to look for: Red Bull GmbH, Am Brunnen 1, 5330, Fuschl am See, Austria
In scope

We are happy to give a wide scope for the researchers, so we consider everything to be in scope that is not out of scope. We ask you kindly to confirm if the files/directories that you may find contains any sensitive information like credentials, personal data and so on.

Please see below what is out of scope.

Out of scope

Domains

  • *.redbull.com.cn.

  • contest-api.redbull.com

  • contest-admin.redbull.com

  • contest-partners.redbull.com

  • wingtips*

  • dp*

  • quiz-api.redbull.com

  • quiz-ui.redbull.com

  • quiz-partners.redbull.com

  • quiz-nyc.redbull.com

  • stage-quiz-ui.redbull.com

  • stage-quiz-admin.redbull.com

  • stage-quiz-partners.redbull.com

  • stage-contest-api.redbull.com

Highlighted

  • Reflected/DOM XSS
  • PHPinfo without any sensitive information (passswords, usernames etc.)

Application

  • Self-XSS
  • CSRF
  • Disclosed or misconfigured Google API keys
  • 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
  • CSV Injection
  • Host Header Injection
  • Sessions not being invalidated (logout, enabling 2FA, pw change,...)
  • 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 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, brute force attacks, heavy fuzzing or mass registrations.
  • 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 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.
  • Reports that state that software is out of date/vulnerable without a proof-of-concept
Rules of engagement

Our promise to you

  • Once the triage period is over a Red Bull employee will get in touch with you regarding your finding as soon as possible
  • 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 😉)
  • You'll limit your acitivity to user accounts that belongs to only you.
  • You won't cause any harm to the brand of Red Bull and/or it's consumers.

Safe harbour for researchers

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

Severity assessment

As a general rule of thumb, severity assessments will be based upon their respective CVSS v3 score, with the factors below taken into account to raise or lower the final severity score: https://kb.intigriti.com/en/articles/3672302-severity-assessment

FAQ

Is it possible to earn any reward?

Yes, we do appreciate the time and effort of each individual researchers and even though we do not give out monetary reward we are happy to award some "Care Package" based on the severity of the reported finding.

Is there a place where I can see what rewards are applicable for specific severities?

Sure, please find more information below.

  • None/Informational - No reward
  • Low - No reward
  • Medium - 1 tray of Red Bull (24pcs. of cans.)
  • High - 3 trays of Red Bull
  • Critical - 6 trays of Red Bull
  • Exceptional - Red Bull Surprise
  • Duplicate - No reward
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
947
average payout
N/A
accepted submissions
290
total payouts
N/A
Last 90 day response times
avg. days first response
0.85
avg. days to decide
6.96
avg. days to triage
1.33
Activity
10/22
logo
jannykhan
created a submission
10/22
logo
oct0pus7
created a submission
10/22
logo
kartikpandey
created a submission
10/22
logo
mase289
created a submission
10/22
Red Bull
closed a submission
10/22
Red Bull
accepted a submission
10/22
Red Bull
accepted a submission
10/22
Red Bull
accepted a submission
10/22
Red Bull
accepted a submission
10/22
Red Bull
accepted a submission