|
1 | 1 | # Security Policy |
2 | 2 |
|
3 | | -## Supported Versions |
| 3 | +This Eclipse Foundation Project adheres to the [Eclipse Foundation Vulnerability Reporting Policy](https://www.eclipse.org/security/policy/). |
4 | 4 |
|
5 | | -| Version | Supported | |
6 | | -| ------- | ------------------ | |
7 | | -| 6.4.x | :white_check_mark: | |
| 5 | +## How To Report a Vulnerability |
8 | 6 |
|
9 | | -## Reporting a Vulnerability |
| 7 | +If you think you have found a vulnerability in this repository, please report it to us through coordinated disclosure. |
10 | 8 |
|
11 | | -If you think you have found a vulnerability in <project> you can report it using one of the following ways: |
| 9 | +**Please do not report security vulnerabilities through public issues, discussions, or change requests.** |
12 | 10 |
|
13 | | -* Contact the [Eclipse Foundation Security Team](mailto:security@eclipse-foundation.org) |
14 | | -* [Report a Vulnerability](https://github.com/eclipse-threadx/usbx/security/advisories/new) |
| 11 | +Instead, [report it privately here](https://github.com/eclipse-threadx/usbx/security/advisories/new) on GitHub |
15 | 12 |
|
16 | 13 | You can find more information about reporting and disclosure at the [Eclipse Foundation Security page](https://www.eclipse.org/security/). |
17 | 14 |
|
18 | | -## Security Policy |
| 15 | +Please include as much of the information listed below as you can to help us better understand and resolve the issue: |
| 16 | + |
| 17 | +* The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting) |
| 18 | +* Affected version(s) |
| 19 | +* Impact of the issue, including how an attacker might exploit the issue |
| 20 | +* Step-by-step instructions to reproduce the issue |
| 21 | +* The location of the affected source code (tag/branch/commit or direct URL) |
| 22 | +* Full paths of source file(s) related to the manifestation of the issue |
| 23 | +* Configuration required to reproduce the issue |
| 24 | +* Log files that are related to this issue (if possible) |
| 25 | +* Proof-of-concept or exploit code (if possible) |
| 26 | + |
| 27 | +This information will help us triage your report more quickly. |
| 28 | + |
| 29 | +## Supported Versions |
| 30 | + |
| 31 | +| Version | Supported | |
| 32 | +| ------- | ------------------ | |
| 33 | +| 6.5.x | :white_check_mark: | |
| 34 | + |
| 35 | +Eclipse ThreadX publishes a release every quarter. There are no long-term support branches or backports to older releases. |
| 36 | + |
| 37 | +Normally, fixes for non-critical vulnerabilities will ship in a regularly scheduled quarterly release. If fixes for an urgent or critical vulnerability must ship quickly, then the project will publish a hotfix release of the affected component(s) without waiting for the next quarterly release. |
19 | 38 |
|
20 | | -This project follows [Eclipse Foundation Vulnerability Reporting Policy](https://www.eclipse.org/security/policy/). |
| 39 | +You can learn more about the [project's release cadence in this blog post](https://blogs.eclipse.org/post/fr%C3%A9d%C3%A9ric-desbiens/eclipse-threadx-more-predictable-more-open). |
0 commit comments