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,074 researchers, 1,651 honor badges

bokadirekt.se Bug Bounty Program

bokadirekt.se 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 bokadirekt.se

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

Bug bounty program allow private and public submissions.

Bug Bounty Scope

The following websites are within the scope of the program:

bokadirekt.se

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:

Vulnerabilities in Bokadirekt's products and services are only within the scope of the Bug Bounty Scheme when they meet the following conditions:

They have not been previously reported or have not already been discovered by our own internal procedures;
It can be demonstrated that there would be a real impact to Bokadirekt,, its users or its customers should the vulnerability reported be exploited by a malicious actor. The existence of a vulnerability does not necessarily demonstrate that such a potential impact exists: theoretical impacts will not be considered within the scope of the scheme;
It exists within a domain that has a security.txt file in its root. Subdomains are considered in the scope provided their parent domain is in scope. (i.e. the existence of https://<bokadirekt.se>/security.txt means that app.bokadirekt.se and www.bokadirekt.se are also in scope.)

Testing Requirements:

The following is out of scope and should not be performed:

- Volumetric/Denial of Service vulnerabilities (i.e. simply overwhelming our service with a high volume of requests);
- TLS configuration weaknesses (e.g. “weak” cipher suite support, TLS1.0 support, sweet32, etc.);
- Reports indicating that our services do not fully align with “best practice” (e.g. missing security headers or suboptimal email-related configurations such as SPF, DMARC, etc.);
- Issues surrounding the verification of email addresses used to create user accounts;
- Clickjacking vulnerabilities;
- Self XSS / DOM Based XSS (i.e. where a user would need to be tricked into pasting code into their web browser);
- CSRF where the resulting impact is minimal;
- CRLF attacks where the resulting impact is minimal;
- Host header injection where the resulting impact is minimal;
- Network data enumeration techniques (e.g. banner grabbing, existence of publicly available server diagnostic pages);
- Reports of improper session management/session fixation vulnerabilities.
- Social engineering or phishing attacks against employees or customers.

Possible Awards:

For confirmed problems we will recommend on your profile and hall of fame.
For very critical problems a monetary reward up to $500 may be awarded.
How critical a problem is deemed to be will be up to Bokadirekt to determine and will be based on the severity of the problem, the impact and other related points.

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

No comments so far.

  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!