You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SECURITY.md
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,18 +12,23 @@ Patches are only released for the latest version.
12
12
13
13
If you believe you have found a security vulnerability, please report it to us through coordinated disclosure.
14
14
15
-
**Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.**
15
+
> [!WARNING]
16
+
> **Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.**
16
17
17
-
Instead, please send an email to opensource[@]drechsel.xyz.
18
+
This gives us time to work with you to fix the issue before public exposure, reducing the chance that the exploit will be used before a patch is released.
19
+
20
+
You may submit the report in the following ways:
21
+
- create a [private vulnerability report](https://github.com/kimdre/doco-cd/security/advisories/new)
22
+
- send an email to opensource[@]drechsel.xyz.
18
23
19
24
Please include as much of the information listed below as you can to help us better understand and resolve the issue:
20
25
26
+
- Impact of the issue, including how an attacker might exploit the issue
27
+
- Step-by-step instructions to reproduce the issue
28
+
- Proof-of-concept or exploit code (if possible)
29
+
- The version and/or location of the affected source code (tag/branch/commit or direct URL)
21
30
- The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
22
31
- Full paths of source file(s) related to the manifestation of the issue
23
-
- The location of the affected source code (tag/branch/commit or direct URL)
24
32
- Any special configuration required to reproduce the issue
25
-
- Step-by-step instructions to reproduce the issue
26
-
- Proof-of-concept or exploit code (if possible)
27
-
- Impact of the issue, including how an attacker might exploit the issue
28
33
29
34
This information will help us triage your report more quickly.
0 commit comments