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,865 coordinated disclosures
1,383,436 fixed vulnerabilities
1,991 bug bounty programs, 3,919 websites
47,069 researchers, 1,651 honor badges

Videsk Bug Bounty Program

Videsk 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 Videsk

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

Bug bounty program allow private submissions only.

Bug Bounty Scope

The following websites are within the scope of the program:

*.videsk.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:

Please bear in mind we are interested in bugs, not user data. If you come across user information during your research, do not save, store, copy, transfer, disclose, or otherwise retain this information and please report it immediately to us.

Note that we are only able to answer technical vulnerability reports. Non-security bugs and queries about problems with your account should be instead directed to our customer support team.

Please perform your research in good faith. Please don’t publicly disclose a vulnerability without our consent and review. Our pledge to you is to respond promptly and fix bugs in a sensible timeframe - and in exchange, we ask for reasonable advance notice.

Reports that go against this principle will usually not qualify, but we will evaluate them on a case-by-case basis.

Any reports related to our customers' infrastructure or services will not be rewarded by us but will be received to notify them. (We'll appreciate it, we hope also them)

Testing Requirements:

More details: https://s.videsk.io

1. Check the out-of-scope reports here: https://s.videsk.io/excluded
2. Send the report by email only: Consider encrypting content and files using the GPG key.
3. Be clear: Please add much information as you need.
4. Reproducible steps: Check the report can be reproduced with the information you provide. If not contains enough info will be labeled as incomplete, discarding the report. (You will be notified)
5. Languages: We accept reports in English and Spanish. Please consider using translators if you don't speak these languages.

The following domains and subdomains are in the scope of valid reports:

- *.videsk.io

Any other domains are out of the scope of this policy. We provide services only on our base and unique domain.

Possible Awards:

We will determine the impact of your reported bug. Broadly speaking, the rewards usually start from USD $10.

In particular, we may decide to pay higher rewards for unusually clever or severe vulnerabilities or pay lower rewards for vulnerabilities that require unusual user interaction.

We may also decide a single report constitutes multiple bugs or that multiple reports are so closely related that they only warrant a single reward.

Videsk rewards bug bounty hunters on a first-come, first-served basis - the first comprehensive report for the same bug will be awarded any bounty.

Special Notes:

We are unable to issue rewards to individuals who are on sanctions lists, or who are in countries (e.g. Cuba, Iran, North Korea, Sudan, and Syria) on sanctions lists. You are responsible for any tax implications depending on your country of residency and citizenship.

Videsk rewards bug bounty hunters on a first-come, first served basis so if you find a vulnerability that has just been reported we will not reward you.

Of course, your testing must not violate any law, or disrupt or compromise any data that is not your own.

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

AshKetchum333     23 March, 2023
    AshKetchum333:
No response from the team
gdattacker     1 December, 2022
    gdattacker:
as you said "Send the report by email only: Consider encrypting content and files using the GPG key." but where is email

  Latest Patched

 26.04.2024 news.gov.mb.ca
 26.04.2024 mdanderson.org
 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

  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!