forked from apache/dubbo
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add security.md
- Loading branch information
Showing
1 changed file
with
31 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Security Policy | ||
|
||
## Supported Versions | ||
|
||
Below is a table that shows versions that accept security fix. | ||
|
||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 2.7.x | :white_check_mark: | | ||
| 2.6.x | :white_check_mark: | | ||
| 2.5.x | :x: | | ||
|
||
|
||
## Reporting a Vulnerability | ||
|
||
The Apache Software Foundation takes a rigorous standpoint in annihilating the security issues in its software projects. Apache Dubbo is highly sensitive and forthcoming to issues pertaining to its features and functionality. | ||
|
||
If you have apprehensions regarding Dubbo's security or you discover vulnerability or potential threat, don’t hesitate to get in touch with the Apache Dubbo Security Team by dropping a mail at [email protected]. In the mail, specify the description of the issue or potential threat. You are also urged to recommend the way to reproduce and replicate the issue. The Dubbo community will get back to you after assessing and analysing the findings. | ||
|
||
PLEASE PAY ATTENTION to report the security issue on the security email before disclosing it on public domain. | ||
|
||
## VULNERABILITY HANDLING | ||
|
||
An overview of the vulnerability handling process is: | ||
|
||
* The reporter reports the vulnerability privately to Apache. | ||
* The appropriate project's security team works privately with the reporter to resolve the vulnerability. | ||
* A new release of the Apache product concerned is made that includes the fix. | ||
* The vulnerability is publically announced. | ||
|
||
A more detailed description of the process can be found [here](https://www.apache.org/security/committers.html). |