- It is amazing that members of the community want to lend their support to this project and help build up the Ransomware Vulnerabilities Matrix.
- Please follow the guidelines below if you wish to contribute.
Important
To contribute to this repository, researchers must follow the How to Contribute guide, otherwise pull requests will be closed without merging them.
- Provide the Vendor and Product Name
- Provide the CVE Number(s) - As sometimes an exploit chain may have multiple CVEs tied to it
- Provide the name of the Ransomware Gang, Affiliate, IAB, or State-Sponsored Ransomware Operator
- Provide Evidence
- Make sure to follow the Markdown Table Format for adding a new row or adding to an existing row:
| Product | CVE(s) | Ransomware Group(s) | Source(s) |
|---|---|---|---|
| product_name | cve_number | group_name | [xyz.com](htttps://LINK_GOES_HERE) |
| product_name | cve_number & cve_number | group_name, group_name | [abc.com](https://xxx) / [xyz.com](https://xxx) |
- The Ransomware Vulnerability Matrix is based on open source intelligence (OSINT) threat reports provided by a variety of sources, such as CISA's #StopRansomware alerts or The DFIR Report's publications, among others.
- Please cite your sources of information for where it was reported that this vulnerability was exploited by a ransomware adversary
- Please do not submit vulnerabilities to this repository if there are no public sources to support your submission
- It is important that others can independently verify your claims
- The quality of the evidence provided shall be judged during a review of the pull request - it may be closed if the evidence is insufficient to support your commit