svc-admin01/snipe-it
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixed typo, added context (“worm”? Really?)

Browse Source
This commit is contained in:
snipe
2026-05-05 22:00:02 +01:00
parent cd4e268c72
commit a425234365
1 changed files with 15 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SECURITY.md
+15 -4
View File
@@ -10,9 +10,9 @@ however there are times when library dependencies and/or PHP/MySQL dependencies
make it impossible to backport security fixes on older versions. make it impossible to backport security fixes on older versions.
| Version | Supported | | Version | Supported |
|---------| ------------------ | |---------|--------------------|
| 8.x | :white_check_mark: | | 8.x | :white_check_mark: |
| 7.x | :white_check_mark: | | 7.x | :x: |
| 6.x | :x: | | 6.x | :x: |
| 5.1.x | :x: | | 5.1.x | :x: |
| 5.0.x | :x: | | 5.0.x | :x: |
@@ -24,7 +24,18 @@ make it impossible to backport security fixes on older versions.
Security vulnerabilities should be sent to security@snipeitapp.com. You can typically expect a Security vulnerabilities should be sent to security@snipeitapp.com. You can typically expect a
response within two business days, and we typically have fixes out in under a week from the initial disclosure. response within two business days, and we typically have fixes out in under a week from the initial disclosure.
This obviously varies based on the severity of the security issue and the difficulty in remediation, This obviously varies based on the severity of the security issue and the difficulty in remediation, but those have
but those have historically been the timelines we worm around. historically been the timelines we work around.
We do ask that you do not disclose the vulnerability publicly until we have had a chance to address it and tag a release
so that we can protect our users, and we will work
with you to coordinate a public disclosure once we have a fix out. We will also work with you to ensure that you receive
appropriate credit for the discovery of the vulnerability, if you would like to be credited. (Please provide a GitHub
username or other information if you would like to be credited, and please let us know if you would like to remain
anonymous.)
For responsible disclosure, we ask that you give us at least __90 days__ to address the issue before disclosing it
publicly,
but we will work with you if you need to disclose it sooner than that.
For a full breakdown of our security policies, please see https://snipeitapp.com/security. For a full breakdown of our security policies, please see https://snipeitapp.com/security.