Acknowledgements / Hall of Fame for security researchers reporting bugs and vulnerabilities in verdigado and Netzbegrünung services. Available at &
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

73 lines
2.9 KiB

verdigado & Netzbegruenung Security and Vulnerability Reporting Policy
1. Services Covered by this Policy
This policy covers all services directly operated by us (verdigado eG &
Netzbegruenung). Services can be identified by the following means:
- The website has a .well-known/security.txt that links to this policy.
- The reverse DNS of an IP address resolves to one of the following
domains: *, *, *
2. Acceptable Use
We generally invite security researchers to search for vulnerabilities
in our services. We kindly ask to not put any actual user data or
production systems at risk.
3. Classification of Vulnerabilities
We will consider a vulnerability report most likely as relevant if it
reports one of the following problems:
- The vulnerability can be used to directly access non-public
information that either reveals further security relevant problems or
contains user data, credentials, or sensitive data in general.
- The vulnerability can be used to disrupt the orderly operation of a
service (Denial of Service).
- The vulnerability can be used to manipulate data within the service.
- XSS, CSRF, RCE, authentication/authorization bypass, SQL inections,
etc are considered relevant.
We will consider a vulnerability report most likely as NOT relevant if
it reports one of the following problems:
- Missing security features, for example HTTP headers, if they are not
actually preventing a vulnerability.
- Publicly accessible version strings of used software.
- Security vulnerablities that can only be used within the scope of the
used account.
4. Reporting Vulnerabilities
Report vulnerabilities via e-mail to
Please make sure that you include the following information:
- Which service is affected
- How can the bug be used/exploited
- Explanation of the risk
Reports will be answered within 48 hours. If you have not received an
answer within that time frame, feel free to contact us again.
For used open source software, we recommend to file bug reports and/or
pull requests against the upstream repositories. This includes hardening
instructions in the installation documentation.
5. Bug Bounties / Rewards
The amount of reward payed depends on the severity of the found
vulnerability. We usually do not pay rewards if vulnerabilities can be
found in mass scans with of-the-shelf software.
Only responsible disclosures are eligible for rewards.
6. Acknowledgement
We list recognized reports of vulnerablities online if the reporting
security researcher agrees. The name, contact e-mail address, and type
of vulnerability can be included in the list. Our public
acknowledgements can be found at
7. About this Policy
This policy is MIT licensed. Feel free to suggest modifications and
additions at