This document defines how security vulnerability reporting is handled in the Hyperledger AnonCreds project. The approach aligns with the Hyperledger Foundation's Security Vulnerability Reporting policy. Please review that document to understand the basis of the security reporting for Hyperledger AnonCreds.

The Hyperledger Security Vulnerability policy borrows heavily from the recommendations of the OpenSSF Vulnerability Disclosure working group. For up-to-date information on the latest recommendations related to vulnerability disclosures, please visit the GitHub of that working group.

If you are already familiar with the security policies of Hyperledger AnonCreds, and ready to report a vulnerability, please jump to Report Intakes.

This document has the following sections:

• Hyperledger AnonCreds Security Policy
  • Instructions
  • About this document
  • Outline
  • What Is a Vulnerability Disclosure Policy?
  • Security Team
  • Discussion Forums
  • Report Intakes
  • CNA/CVE Reporting
  • Embargo List
  • (GitHub) Security Advisories
  • Private Patch Deployment Infrastructure

No piece of software is perfect. All software (at least, all software of a certain size and complexity) has bugs. In open source development, members of the community or the public find bugs and report them to the project. A vulnerability disclosure policy explains how this process functions from the perspective of the project.

This vulnerability disclosure policy explains the rules and guidelines for Hyperledger AnonCreds. It is intended to act as both a reference for outsiders–including both bug reporters and those looking for information on the project’s security practices–as well as a set of rules that maintainers and contributors have agreed to follow.

The current Hyperledger AnonCreds security team is:

The security team for Hyperledger AnonCreds must include at least three project Maintainers that agree to carry out the following duties and responsibilities. Members are added and removed from the team via approved Pull Requests to this repository. For additional background into the role of the security team, see the People Infrastructure section of the Hyperledger Security Policy.

Responsibilities:

1. Acknowledge the receipt of vulnerability reports to the reporter within 2 business days.

2. Assess the issue. Engage with the reporter to ask any outstanding questions about the report and how to reproduce it. If the report was received by email and may be a security vulnerability, open a GitHub Security Advisory on the repository to manage the report. If the report is not considered a vulnerability, then the reporter should be informed and this process can be halted. If the report is a regular bug (but not a security vulnerability), the reporter should be informed (if necessary) of the regular process for reporting issues.

3. Some issues may require more time and resources to correct. If a particular report is complex, discuss an embargo period with the reporter during which time the report will not be publicly disclosed. The embargo period should be negotiated with the reporter and must not be longer than 90 days.

4. If necessary, create a private patch development infrastructure for the issue by emailing the Hyperledger Community Architects.

5. Request a CVE for the issue (see the CNA/CVE Reporting section).

6. Decide a date for the public release of the vulnerability report, the date the embargo period ends.

7. If applicable, notify members of the embargo list of the vulnerability, upcoming patch and release, as described above.

8. Publish a new (software) release in which the vulnerability is addressed.

9. Publicly disclose the issue within 48 hours after the release via a GitHub security advisory (see the (GitHub) Security Advisories section for details).

Discussions about each reported vulnerability should be carried out in the private GitHub security advisory about the vulnerability. If necessary, a private channel specific to the issue may be created on the Hyperledger Discord server with invited participants added to the discussion.

Hyperledger AnonCreds has the following ways to submit security vulnerabilities. While the security team members will do their best to respond to bugs disclosed in all possible ways, it is encouraged for bug finders to report through the following approved channels:

• Email the Hyperledger Foundation security list: To report a security issue, please send an email with the name of the project/repository, a description of the issue, the steps you took to create the issue, affected versions, and if known, mitigations. If in triaging the email, the security team determines the issue may be a security vulnerability, a GitHub security vulnerability report will be opened.
• Open a GitHub security vulnerability report: Open a draft security advisory on the "Security" tab of this GitHub repository. See GitHub Security Advisories to learn more about the security infrastructure in GitHub.

Hyperledger AnonCreds maintains a list of Common Vulnerabilities and Exposures (CVE) and uses GitHub as its CVE numbering authority (CNA) for issuing CVEs.

Hyperledger AnonCreds maintains a private embargo list. If you wish to be added to the embargo list, please email the Hyperledger Foundation security mailing list, including the project name (Hyperledger AnonCreds) and reason for being added to the embargo list. Requests will be assessed by the Hyperledger AnonCreds security team in conjunction with the appropriate Hyperledger Staff, and a decision will be made to accommodate or not the request.

For more information about the embargo list, please see the Embargo List section of the Hyperledger Security Policy.

Hyperledger AnonCreds uses GitHub Security Advisories to manage the public disclosure of security vulnerabilities.

In creating patches and new releases that address security vulnerabilities, Hyperledger AnonCreds uses the private development features of GitHub for security vulnerabilities. GitHub has extensive documentation about these features.