Coordinated and Responsible Vulnerability Disclosure Free Bug Bounty Program 454,221 coordinated disclosures
242,780 fixed vulnerabilities
601 bug bounties with 1221 websites
12,269 researchers, 960 honor badges

EMBL-EBI Bug Bounty Program

EMBL-EBI 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 EMBL-EBI

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

Bug bounty program allow private and public submissions.

Bug Bounty Scope

The following websites are within the scope of the program:


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:

Keeping the information we hold secure is of the utmost importance to EMBL-EBI. We value any contribution made by those outside the organisation in improving the security of our services. We are committed to working with the community to verify, reproduce, and respond to legitimate reported vulnerabilities. We encourage the community to participate in our responsible reporting process which applies to services relating to the following domains:


Testing Requirements:

We will assess all reports and investigate those reports satisfying the following criteria. We will make every effort to correct any vulnerability within 6 months. To encourage responsible reporting, we commit that we (EMBL) will not take legal action against you or ask law enforcement to investigate you if you comply with the following Responsible Disclosure Guidelines:

- Reporter to provide details of the vulnerability, including information needed to reproduce and validate the vulnerability and a Proof of Concept (POC)
- Reporter to give us up to 6 months to correct the issue before making any information public
- Reporter to make a good faith effort to avoid privacy violations, destruction of data and interruption or degradation of our services
- Reporter does not modify or access non-public data, or data that is not theirs
- Reporter to refrain from requesting compensation for reporting vulnerabilities. Upon request we will publicly acknowledge reporter’s responsible disclosure after issues are resolved.
- Reporter to refrain from using automated tools to scan for vulnerabilities, as this can have an adverse effect on other users of our services.

Possible Awards:

Reporter to refrain from requesting compensation for reporting vulnerabilities. Upon request we will publicly acknowledge reporter’s responsible disclosure after issues are resolved.

Special Notes:

We will attempt to respond to your report within 5 working days (we are closed over Christmas and New Year).

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

    13 July, 2019
I found open FTP with details. share mail for send details. Thank you.
    11 July, 2019
please share your mail address for other report

  Latest Patched


  Latest Blog Posts

17.10.2019 by geeknik
The "S" in IOT is for Security
16.10.2019 by darknetguy
Best XSS Vectors
01.10.2019 by Renzi25031469
#Security 100%
18.09.2019 by Leon
SSRF | Reading Local Files from DownNotifier server
13.09.2019 by drok3r
Collection of information | Google Hacking and Dorks basic

  Recent Recommendations

    18 October, 2019
Thank you 0xrocky for identifying a vulnerability and making us aware of it. Great security researcher to work with. Keep up the good work!
    17 October, 2019
A kudos to 0xrocky for his professional work in not using the identified vulnerabilities and alerting us
    17 October, 2019
Thanks for the hint :)
Good work.
    17 October, 2019
Thanks to 0xrocky for identifying the vulnerability. Now we patched the vulnerability.
    17 October, 2019
Thank you very much for making us aware of the issue and providing us a high quality vulnerability report which helped us identify the source of the vulnerability right away.