Skip to content

Commit f48b18d

Browse files
authored
Merge branch 'main' into feat/1026-concurrent-deployments
2 parents 68d7c2d + b673b8c commit f48b18d

File tree

1 file changed

+11
-6
lines changed

1 file changed

+11
-6
lines changed

SECURITY.md

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,18 +12,23 @@ Patches are only released for the latest version.
1212

1313
If you believe you have found a security vulnerability, please report it to us through coordinated disclosure.
1414

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.**
1617
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.
1823

1924
Please include as much of the information listed below as you can to help us better understand and resolve the issue:
2025

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)
2130
- The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
2231
- 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)
2432
- 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
2833

2934
This information will help us triage your report more quickly.

0 commit comments

Comments
 (0)