Security Reporting
For more details on active Security Policies, checkoutthis page.
Reporting a bug in Node.js
Report security bugs in Node.js viaHackerOne.
Normally, your report will be acknowledged within 5 days, and you'll receivea more detailed response to your report within 10 days indicating thenext steps in handling your submission. These timelines may extend whenour triage volunteers are away on holiday, particularly at the end of theyear.
After the initial reply to your report, the security team will endeavor to keepyou informed of the progress being made towards a fix and full announcement,and may ask for additional information or guidance surrounding the reportedissue.
Node.js bug bounty program
The Node.js project engages in an official bug bounty program for securityresearchers and responsible public disclosures. The program is managed throughthe HackerOne platform. Seehttps://hackerone.com/nodejs for further details.
Reporting a bug in a third party module
Security bugs in third party modules should be reported to their respectivemaintainers.
Disclosure policy
Here is the security disclosure policy for Node.js
The security report is received and is assigned a primary handler. Thisperson will coordinate the fix and release process. The problem is validatedagainst all supported Node.js versions. Once confirmed, a list of all affectedversions is determined. Code is audited to find any potential similarproblems. Fixes are prepared for all supported releases.These fixes are not committed to the public repository but rather held locallypending the announcement.
A suggested embargo date for this vulnerability is chosen and a CVE (CommonVulnerabilities and Exposures (CVE®)) is requested for the vulnerability.
On the embargo date, a copy of the announcement is sent to the Node.jssecurity mailing list. The changes are pushed to the public repository and newbuilds are deployed to nodejs.org. Within 6 hours of the mailing list beingnotified, a copy of the advisory will be published on the Node.js blog.
Typically, the embargo date will be set 72 hours from the time the CVE isissued. However, this may vary depending on the severity of the bug ordifficulty in applying a fix.
This process can take some time, especially when we need to coordinate withmaintainers of other projects. We will try to handle the bug as quickly aspossible; however, we must follow the release process above to ensure that wehandle disclosure consistently.
Receiving security updates
Security notifications will be distributed via the following methods.
Comments on this policy
If you have suggestions on how this process could be improved, please visitthenodejs/security-wgrepository.
OpenSSF Best Practices
The Open Source Security Foundation (OpenSSF)Best Practices badge is a way for Free/Libre and Open Source Software (FLOSS) projects to show that they follow best practices. Projects can voluntarily self-certify how they follow each best practice. Consumers of the badge can quickly assess which FLOSS projects are following best practices and as a result are more likely to produce higher-quality secure software.