Infosec Institute

Open Bug Bounty mentioned in the
Top 6 Bug Bounty programs of
2022 by the InfoSec Institute

The Hacker News

Open Bug Bounty named among the
Top 5 Bug Bounty programs of 2021
by The Hacker News

Platform update: please use our new authentication mechanism to securely use the Open Bug Bounty Platform.
For security researchers
Report a Vulnerability
Submit, help fixing, get kudos.
For website owners
Start a Bug Bounty
Run your bounty program for free.
1,704,662 coordinated disclosures
1,383,264 fixed vulnerabilities
1,991 bug bounty programs, 3,919 websites
47,027 researchers, 1,651 honor badges

CenturyLink Public Cloud Bug Bounty Program

CenturyLink Public Cloud 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 CenturyLink Public Cloud

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

Bug bounty program allow private submissions only.

Bug Bounty Scope

The following websites are within the scope of the program:

*.ctl.io

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:

Only Domains under ctl.io are allowed as CenturyLink proper does not currently have a BugBounty program. Any reports regarding CenturyLink, Level3, or any other business units of CenturyLink should not be reported to this program.

Testing Requirements:

All vulnerabilities should be verified and not results of an automated tool. Automated tools should also be avoided so that a denial of service isn't created against our services. We are not interested in reports about

* Software version disclosure
* Attempts to physically access our offices or data centers
* Social engineering attempts on our staff or experts including phishing emails
* Vulnerabilities in a vendor we integrate with
* Email infrastructure, particularly our use of (or lack of) SPF, DKIM and DMARC.
* Use of automated tools that could generate significant traffic and possibly impair the functioning of our application
* Vulnerabilities that cannot be reproduced

We are interested in

* Cross-Site-Scripting (XSS)
* Cross-Site Request Forgery (CSRF)
* Clickjacking
* Open forwards / Open redirects
* Datastore/SQL Injection
* Remote Code Execution
* Directory Traversal
* Content Spoofing
* Denial of Service not relating to a distributed attack

Please provide a detailed description and steps to reproduce your finding.

Possible Awards:

We can offer recognition and in the most critical cases, offer some level of free credits towards a CenturyLink Public Cloud account. You should already have an account created or be able to create an account so that we can apply the credits properly. Credits are not a guaranteed reward.

Special Notes:

Everyone is eligible for $500 in free trial credits initially. See https://www.ctl.io/knowledge-base/general/centurylinkcloud/free-trial-faq/ for details. If you disclose NEW findings we may be able to credit your account accordingly.

All accounts must be verifiable and not used for any fraudulent activity. Account holders must also remain in compliance with our Acceptable Use Policy. While testing against one's own account may be necessary, attempting to access any account that is not yours is a violation of our AUP. If you discover a vulnerability that would give you access to another account or data for another account. Please stop testing and notify us immediately so that we can validate and remediate the findings.

Other Submissions Handling

Website owner want to receive information about other vulnerabilities

Notifications:

Same as above. however, you may need to send an email to [email protected] so that we can receive the report as OBB won't track those for us.

General Requirements:

Same as above

Testing Requirements:

Same as above

Possible Awards:

Same as above

Special Notes:

Same as above

Community Rating

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

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

Researcher's comments

KhanJanny     16 February, 2022
    KhanJanny:
no one response
Wh0ami_7     21 May, 2020
    Wh0ami_7:
CenturyLink Sec team were quick to fix my submission. Props to the platform security lead who communicated the fix and for the reward.

  Latest Patched

 25.04.2024 seeu.edu.mk
 25.04.2024 xaxim.sc.gov.br
 25.04.2024 lacerdopolis.sc.gov.br
 24.04.2024 tap.mk.gov.lv
 23.04.2024 data.aad.gov.au
 23.04.2024 bitporno.to
 23.04.2024 sys01.lib.hkbu.edu.hk
 23.04.2024 srvm.gov.za
 22.04.2024 stc.edu.hk
 22.04.2024 friv5online.com

  Latest Blog Posts

04.12.2023 by BAx99x
Unmasking the Power of Cross-Site Scripting (XSS): Types, Exploitation, Detection, and Tools
04.12.2023 by a13h1_
$1120: ATO Bug in Twitter’s
04.12.2023 by ClumsyLulz
How I found a Zero Day in W3 Schools
04.12.2023 by 24bkdoor
Hack the Web like a Pirate: Identifying Vulnerabilities with Style
04.12.2023 by 24bkdoor
Navigating the Bounty Seas with Open Bug Bounty

  Recent Recommendations

    22 April, 2024
    genoverband:
Thank you for your invaluable help in ensuring the security of our domain and its visitors!
    10 April, 2024
    Mars:
Hatim uncovered a XSS bug that we were able to quickly resolve. Thanks very much for your assistance and help.
    8 April, 2024
    Panthermedia:
Thanks to the support of Hatim Chabik, we were able to identify and solve an XSS bug.
    5 April, 2024
    pubpharm:
Pooja found a XSS vulnerability on our website and provided us with the needed Information for replication and fixing the issue. Which she verified afterwards.
We thank her for the reporting and assistance.
    2 April, 2024
    genoverband:
Thank you for your invaluable help in ensuring the security of our domain and its visitors!