Bug Bounty Program

    If you believe you have found a security vulnerability in TeamSpeak client or server, we encourage you to let us know right away. We will investigate all legitimate reports. Before reporting though, please review this page including our reward guidelines and those things that should not be reported.
    We recognize and reward security researchers who help us keep people safe by reporting vulnerabilities in TeamSpeak services. Monetary bounties for such reports are entirely at R4P3’s discretion, based on risk, impact, and other factors. To potentially qualify for a bounty, you first need to meet the following requirements:

    • Report a security bug: that is, identify a vulnerability in TeamSpeak services or infrastructure which creates a security or privacy risk. (Note that R4P3 ultimately determines the risk of an issue, and that many software bugs are not security issues.)
    • We specifically exclude certain types of potential security issues; these are listed under “Ineligible Reports and False Positives” (see below).
    • Submit your report via our “Report a Security Vulnerability” form (one issue per report) and respond to the report with any updates. Please do not contact employees directly or through other channels about a report.
    • If you inadvertently cause a privacy violation or disruption (such as accessing account data, service configurations, or other confidential information) while investigating an issue, be sure to disclose this in your report.
    • Use test accounts when investigating issues. If you cannot reproduce an issue with a test account, you can use a real account (except for automated testing).

    In turn, we will follow these guidelines when evaluating reports under our bug bounty program:
    • We investigate and respond to all valid reports. Due to the volume of reports we receive, though, we prioritize evaluations based on risk and other factors, and it may take some time before you receive a reply.
    • We determine bounty amounts based on a variety of factors, including (but not limited to) impact, ease of exploitation, and quality of the report. If we pay a bounty, the minimum reward is 1 month of VIP membership. Note that extremely low-risk issues may not qualify for a bounty at all.
    • We seek to give similar rewards for similar issues, but bounty amounts and qualifying issues may change with time. Past rewards do not necessarily guarantee similar results in the future.
    • In the event of duplicate reports, we award a bounty to the first person to submit an issue. (R4P3 determines duplicates and may not share details on the other reports.) A given bounty is only paid to one individual.
    • You may donate a bounty to a recognized charity (subject to approval by R4P3).
    • We reserve the right to publish those security issues.
    • We publish a list of researchers who have submitted valid security reports. You must receive a bounty to be eligible for this list, but your participation is then optional. We reserve the right to limit or modify the information accompanying your name in the list.

    Attributes of a Good Report
    • Detailed steps in your message explaining how to reproduce the bug. This should include any links you clicked on, pages you visited, URLs, user IDs, etc. Images and video can be helpful if you also include written explanations.
    • Clear descriptions of any accounts used in your report and the relationships between them. Please do not use the same name on multiple accounts to avoid confusion.
    • Quality before quantity. Many of our highest-paid reports had just a few lines of precise, clear explanations.
    • If you send a video, consider these tips:
      • Keep it short by showing only the parts necessary to demonstrate the bug once. (Remove or redo mistakes that might happen while recording.)
      • Record at a resolution where text or URLs are readable (at least 480p; 1080p is usually not necessary).
      • Provide commentary or instructions in your messages or video description instead of typing on-screen during the video.
      • Setting Facebook to English while recording steps helps us quickly identify what features you use.
      • If a large amount of text appears in your video, please include a copy in your messages as well.
      • Keep the video private either by uploading it as an attachment or posting it privately online (such as with a hidden link or password that you send to us).

    Ineligible Reports and False Positives
    • Any bugs which are already reported at www.teamspeak.com
    • Bugs which only affect your local TeamSpeak client and can only be triggered by yourself. Please note you will not get any rewards, but you are eligible for our list of researchers.
    This list may be changed at any time without notice. This does not affect reports we already received.
    To send us your report, please create a new thread here (preferred) or send us an email to admin@r4p3.net

    Wall of Fame:
  • indect