Critical infrastructures and other companies with reporting obligations: manage an incident, report, inform, prevent
BSI CVD guideline for security researchers
If you have found a technical vulnerability in one of the German Government's systems, you can report this to the Computer Emergency Response Team (CERT)-Bund that is part of the Federal Office for IT-Security (BSI). We expect that the Coordinated Vulnerability Disclosure (CVD) guideline of the BSI is followed. You can read here how the BSI deals with vulnerability reports as part of a CVD process (only available in German).
If you found a vulnerability in an IT system or IT product that does not belong to the German Government, the vulnerability should first be reported to the owner of the system or the manufacturer.
We promise,
- To keep each vulnerability report confidential to the extent permitted by law
- not to pass on personal data to third parties without your explicit consent
- to give feedback on every vulnerability report made.
- not to pursue criminal charges against you as long as you have complied with the Policy and Principles. This does not apply if recognizable criminal intentions have been or are being pursued.
- to be the contact person for a trusting exchange throughout the entire process.
- after completion of a CVD process, if desired, to publish your name/alias and a desired reference on the BSI's acknowledgment website.
If you have provided personal data in the report or in the report form, please note the BSI's information on data protection: https://www.bsi.bund.de/EN/Service/PrivacyPolicy/privacypolicy_node.htmlNotes on reporting offices are contained in Section 10 in particular.
We expect from you:
- The vulnerability found was not abused. This means that no damage was caused beyond the reported vulnerability.
- No attacks (such as social engineering, spam, (distributed) DoS or "brute force" attacks, etc.) were carried out against IT systems or infrastructures.
- No manipulation, compromise or modification of possible systems or data of third parties was carried out.
- No tools for exploiting vulnerabilities have been offered for a fee or free of charge that third parties could use to commit crimes.
- The vulnerability reports are not results of automated tools or scans without supporting documentation. These are not valid vulnerability reports.
- The vulnerability report relates to previously unknown information. Your report will be checked for vulnerabilities that have already been fixed, but they do not qualify for further processing as part of the CVD process.
- Valid contact data (e-mail address) is stored so that we can contact you in the case of further inqueries regarding your report. In the case of complex vulnerabilities in particular, it can not be ruled out that we will need further explanations and documentation. Since good communication is important during a CVD case, vulnerability reports without communication options (i.e. valid contact data) are only processed to a limited extent.
In the case of an anonymous report, it must be taken into account that technical and content-related queries from the BSI and/or the manufacturer cannot be made nor answered and corresponding vulnerability reports can therefore only be processed to a limited extent or possibly not at all.
Vulnerability reporting form
In order to support those who find vulnerabilities, the BSI can help with contacting the manufacturer/product owner of an IT system or IT product.
Vulnerabilities can be reported to CERT-Bund using the reporting form:
https://www.bsi.bund.de/Schwachstellenmeldung
If desired, the report can be submitted anonymously. In this case, please ensure that you provide the most comprehensive and precise information possible, which allows us to verify and evaluate the vulnerability, since inquires by the BSI are not possible.
As the reporting party, you determine the extent to which your involvement is disclosed to the manufacturer. Use the last input fields of the form in particular, to let us know.
Vulnerability reports via E-Mail
Researchers who use their own reporting format (e.g. via PDF or txt) can also send vulnerability reports and coordination requests directly to the BSI at vulnerability@bsi.bund.de.
A vulnerability report has to contain the following information:
- The name of the manufacturer/product owner and whether contact was established with them.
- The name of the product and the tested version number.
- A simple description (if necessary screenshots or other illustrations for better comprehensibility) showing how the vulnerability was discovered (including any tools used).
- An assignment of the vulnerability to the OWASP Top 10 2021 (see https://owasp.org/www-project-top-ten). If none of the vulnerability categories fit, this should be described in more detail as "Other"
- Must include proof-of-concept (PoC) code or instructions showing how the vulnerability can be exploited.
- An (informal) declaration of consent to include a name/alias in the recognition website (Hall of Fame) of the BSI if desired
- A risk assessment, taking into account the technical conditions to determine the severity of the vulnerability (e.g. by using a CVSS value and the associated matrix -- preferably in the most current version).
- A description of the impact of the reported vulnerability or a threat model that describes a relevant attack scenario.