|
2 | 2 |
|
3 | 3 | ## Supported Versions |
4 | 4 |
|
5 | | -Only the latest version. |
| 5 | +Only the latest released version. |
| 6 | + |
| 7 | +If you found a vulnerability that only applies to older versions but has been accidentally fixed recently, please open a private advisory to let us evaluate if a backdated advisory is necessary. |
| 8 | + |
| 9 | +If you found a vulnerability in unreleased code (Git trunk), please verify that the latest release is not affected and then use the public issue and pull request workflow to submit your research. |
6 | 10 |
|
7 | 11 | ## Reporting a Vulnerability |
8 | 12 |
|
9 | 13 | Please report (suspected) security vulnerabilities to |
10 | | -**[gotify@protonmail.com](mailto:gotify@protonmail.com)**. You will receive a |
11 | | -response from us within a few days. If the issue is confirmed, we will release a |
| 14 | +[GitHub Advisory](https://github.com/gotify/server/security/advisories/new) |
| 15 | +or **[gotify@protonmail.com](mailto:gotify@protonmail.com)**. |
| 16 | +You will receive a response from us within a few days. |
| 17 | + |
| 18 | +To reduce paperwork and align with CVE key details phrasing, |
| 19 | +an executive summary containing the following elements is sufficient for most reports: |
| 20 | + |
| 21 | +- The affected component (package, file, function, etc) |
| 22 | +- The root cause (weakness in code, insecure default, misleading documentation, etc) |
| 23 | +- The attack model (precondition, vector, impact) |
| 24 | +- A PoC |
| 25 | + |
| 26 | +If the issue is confirmed, we will release a |
12 | 27 | patch as soon as possible. |
| 28 | +Additionally, we will submit findings that demonstrate the necessity for |
| 29 | +user triage to the GitHub CNA Program. |
0 commit comments