Report a Vulnerability
Submit, help fixing, get kudos.
Start a Bug Bounty
Run your bounty program for free.
534,464 coordinated disclosures
334,848 fixed vulnerabilities
786 bug bounties with 1,554 websites
16,006 researchers, 1101 honor badges

A1 Telekom Austria Bug Bounty Program

A1 Telekom Austria runs a bug bounty program to ensure the highest security and privacy of its websites. Everyone is eligible to participate in the program subject to the below-mentioned conditions and requirements of A1 Telekom Austria

Open Bug Bounty performs triage and verification of the submissions. However, we never intervene to the further process of vulnerability remediation and disclosure between A1 Telekom Austria and researchers.

Bug bounty program allow private submissions only.

Bug Bounty Scope

The following websites are within the scope of the program:

*.a1.net
a1.net

Non-Intrusive Submissions Handling

The following section encompasses submission of the vulnerabilities that do not require intrusive testing as per Open Bug Bounty rules:

- Cross Site Scripting (XSS)
- Open Redirect

- Cross Site Request Forgery (CSRF)
- Improper Access Control

General Requirements:

• You can exploit the vulnerability for demonstration purpose, but this should not lead to service outages (DoS) as well as the manipulation or loss of data. The purpose of the demonstration should show the attack vector and should not cause any damage.
• Do not share gathered information with third parties.
• Please make sure to provide enough information so that we can reproduce the issue. A short description including a problem description and the URL/IP of the affected system should be sufficient.

Testing Requirements:

• These areas/fields are not part of the responsible disclosure process:
o Physical security
o Social engineering
o Distributed Denial of Service (DDoS) attacks
o Spam & Phishing
o Exploiting vulnerabilities on systems which are dedicated to our customers

Possible Awards:

At the moment there are no rewards, but this might change in the near future.

Special Notes:

https://www.a1.net/responsible-disclosure

Community Rating

Provided by security researchers who reported security vulnerabilities via this bug bounty program:

 
Response Time  How quickly researchers get responses to their submissions.
Remediation Time  How quickly reported submissions are fixed.
Cooperation and Respect  How fairly and respectfully researchers are being treated.

Researcher's comments

    2 August, 2019
    th3cyb3rc0p:
i reported one bug & it's fixed.can you provide me recommendation letter or thanks?
    29 April, 2019
    ssshah2131:
I reported vulnerability it's almost 15 days but no response from their security team.

  Latest Patched

 02.06.2020 ebi.ac.uk
 02.06.2020 senate.la.gov
 02.06.2020 lra.louisiana.gov
 02.06.2020 upm.es
 02.06.2020 deakin.edu.au
 01.06.2020 fullkade.com
 01.06.2020 gamemodding.com
 01.06.2020 deezer.com
 01.06.2020 iienstitu.com

  Latest Blog Posts

04.04.2020 by Rando02355205
(Alibaba) message.alibaba.com [IDOR] - [Bug Bounty]
12.03.2020 by Rando02355205
(Paypal) www.paypal.com [CSP High Level] - [XSS Reflected] - [Bug Bounty] - [Write Up]
08.03.2020 by CybeReports
JDECO.net XSS Vulnerability| CybeReports
29.02.2020 by Rando02355205
(Google) groups.google.com - [Stored XSS] - [Bug Bounty] - [WriteUp] - [24/02/2020]
10.02.2020 by 0xrocky
Stored XSS on h2biz.net

  Recent Recommendations

    2 June, 2020
     leshaqe:
Thank you for making the web a better place. Professional and helpful contact.
    2 June, 2020
     PaulSaraber:
Thanks for reporting the vulnerability, and the detailed explanation of the mechanism and possible effects. This really contibuted to a quick resolution, the site developer exactly knew where to find and how t fix the issue.

All fixed, many thanks
    1 June, 2020
     atau10614405:
Thanks Aaryan for reporting the vulnerability about xxs.
We will soon fix the problem
    31 May, 2020
     nidapo5:
Brilliant detection of two devious vulnerabilities, with clear explanations which meant I was able to fix both of them very quickly. Many many thanks
    28 May, 2020
     georgekgk:
Thank you Daniel for helping us to find and fix that security issue!