Reporting a Bug in Node.js

All security bugs in Node.js are taken seriously. Please report any security issues here.

Your report will be acknowledged within 5 days, and you’ll receive a more detailed response within 10 days indicating the next steps in handling your report.

After the initial reply to your report, the security team will endeavor to keep you informed of the progress being made towards a fix and full announcement, and may ask for additional information or guidance surrounding the reported issue.

Reporting a Bug in a third party module

Third-party modules are no longer handled by the Node.js security-group. Vulnerabilities in npm packages should be reported directly to the package maintainers. We strongly advise doing this privately. You can find contact information about package maintainers with npm owner ls <package-name>. If the source code is hosted on GitHub please refer to the repository's Security Policy.

Disclosure Policy

Here is the security disclosure policy for Node.js

• The security report is received and is assigned a primary handler. This person will coordinate the fix and release process. The problem is confirmed and a list of all affected versions is determined. Code is audited to find any potential similar problems. Fixes are prepared for all releases which are still under maintenance. These fixes are not committed to the public repository but rather held locally pending the announcement.

• A suggested embargo date for this vulnerability is chosen and a CVE (Common Vulnerabilities and Exposures (CVE®)) is requested for the vulnerability.

• On the embargo date, the Node.js security mailing list is sent a copy of the announcement. The changes are pushed to the public repository and new builds are deployed to nodejs.org. Within 6 hours of the mailing list being notified, 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 is issued. However, this may vary depending on the severity of the bug or difficulty in applying a fix.

• This process can take some time, especially when coordination is required with maintainers of other projects. Every effort will be made to handle the bug in as timely a manner as possible, however, it’s important that we follow the release process above to ensure that the disclosure is handled in a consistent manner.

Receiving Security Updates

Security notifications will be distributed via the following methods.

• https://groups.google.com/group/nodejs-sec

• https://nodejs.org/en/blog

Comments on this Policy

If you have suggestions on how this process could be improved, please submit a pull request or file an issue.

Thank you for improving the security of Node.js and its ecosystem. Your efforts and responsible disclosure are greatly appreciated and will be acknowledged.

Internet Bug Bounty Qualification

The Internet Bug Bounty awards security research on Node.js. If your vulnerability meets the eligibility criteria, you can submit the post-fix information to the IBB for payout. As the IBB supports the whole vulnerability lifecycle, these bounty awards are awarded as an 80/20 split, where 80% will go to you, the finder, and 20% will be given to Node.js to continue to support the vulnerability remediation efforts.

Only vulnerabilities in Node.js core will be considered for eligibility. Submissions related to nodejs.org and other project websites are explicitly NOT eligible.

To submit eligible vulnerabilities for a payout go to https://hackerone.com/ibb for submission instructions after the project maintainers have resolved the vulnerability.

Project Modifiers. Bounty amounts for this project are adjusted based on the following criteria:

>-50% : Vulnerability is not exploitable in a default configuration of Node.js

>-25%: A proposed patch was not provided for the issue

Reminder, be professional! ? Any report of abuse or unprofessional conduct when working with Node.js Maintainers will result in the finder being ineligible for the IBB bounty reward. For example, threats of bad publicity, lack of interest in pragmatic exploitability discussions, refusal to be an active participant in moving resolution forward.

These modifiers are designed to encourage research into the most impactful areas. They are subject to change at any time by the project maintainers.

The project maintainers have final decision on which issues constitute security vulnerabilities. The IBB team will respect their decision, and we ask that you do as well.