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,709,227 coordinated disclosures
1,357,593 fixed vulnerabilities
1,980 bug bounty programs, 3,897 websites
46,087 researchers, 1,643 honor badges

Bentley Systems Bug Bounty Program

Bentley Systems 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 Bentley Systems

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

Bug bounty program allow private submissions only.

Bug Bounty Scope

The following websites are within the scope of the program:

*.bentley.com

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:

Bentley Systems requires that all researchers:
- Avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
- Perform research only within the scope set out below;
- Use the communication channels defined below to report vulnerability information to us;
- Keep information about any vulnerabilities you have discovered confidential between yourself and Bentley Systems until it is fixed.

If you follow these guidelines when reporting an issue to us, we commit to:
- Not pursue or support any legal action related to your research;
- Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 hours of submission);

Testing Requirements:

DoS is strictly forbidden.
Any form of credentials brute forcing is strictly forbidden.
Publicly disclose a vulnerability reported before it has been fixed
(within the grace period) is forbidden.
Do not destroy or degrade our performances or violate the privacy or integrity of users or their data.
Exploiting vulnerabilities, besides a generic PoC is strictly forbidden and will be prosecuted according the law.
If a vulnerability provides unintended access to data: Limit the amount of data you access to the minimum required for effectively demonstrating a Proof of Concept; and cease testing and submit a report immediately if you encounter any user data during testing, such as Personally Identifiable Information (PII), Personal Healthcare Information (PHI), credit card data, or proprietary information.
Do not engage in extortion (i.e. Claims for compensation as a condition for sending in a vulnerability will not be tolerated.).

Possible Awards:

The value of awards, if any, will be determined at the resolution of the incident. There are no guarantee that a reward will be awarded for a submission.

Special Notes:

Unless otherwise informed of the resolution of the vulnerability, we ask the researcher to withhold for a period of 90 days before publicly disclosing the vulnerability. Failure to do so could result in legal actions.

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

ViViDeK     24 July, 2021
    ViViDeK:
I like this program alot, currently spending decent amount of time on it.

  Latest Patched

 28.03.2024 jarchi.me
 28.03.2024 auctionbidding.fcc.gov
 28.03.2024 moodle.wns.gov.il
 28.03.2024 th.adi.gov.il
 28.03.2024 montague-ma.gov
 28.03.2024 aparecida.sp.gov.br
 27.03.2024 nccupress.nccu.edu.tw
 26.03.2024 schedule.cc.nih.gov
 26.03.2024 floraargentina.edu.ar

  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

    20 March, 2024
    TechVitaverdura:
Great exchanges with this person, thank you for your help and your report
    20 March, 2024
    Mek:
He reported some vulnerabilities and oversights of security best practices on my small private project web page.
Was responsive to e-mail, unlike many other people, so yes, I can recommend him.
    20 March, 2024
    ztwo79:
We would like to thank Pooja for responsibly disclosing a Cross-Site Scripting (XSS) vulnerability in our website. Her prompt reporting and assistance in developing a fix were instrumental in ensuring the security of our users.
    16 March, 2024
    TorutheRedFox:
Thanks for the help with the XSS vulnerability. It was a quick fix.
    15 March, 2024
    adesignguy:
Reported an XSS vulnerability which was helpful and much appreciated. I have patched it now as soon as I saw the email which was forwarded onto me!