1# Security 2 3## Reporting a bug in Node.js 4 5Report security bugs in Node.js via [HackerOne](https://hackerone.com/nodejs). 6 7Your report will be acknowledged within 24 hours, and you’ll receive a more 8detailed response to your report within 48 hours indicating the next steps in 9handling your submission. 10 11After the initial reply to your report, the security team will endeavor to keep 12you informed of the progress being made towards a fix and full announcement, 13and may ask for additional information or guidance surrounding the reported 14issue. 15 16### Node.js bug bounty program 17 18The Node.js project engages in an official bug bounty program for security 19researchers and responsible public disclosures. The program is managed through 20the HackerOne platform. See <https://hackerone.com/nodejs> for further details. 21 22## Reporting a bug in a third party module 23 24Security bugs in third party modules should be reported to their respective 25maintainers and should also be coordinated through the Node.js Ecosystem 26Security Team via [HackerOne](https://hackerone.com/nodejs-ecosystem). 27 28Details regarding this process can be found in the 29[Security Working Group repository](https://github.com/nodejs/security-wg/blob/HEAD/processes/third_party_vuln_process.md). 30 31Thank you for improving the security of Node.js and its ecosystem. Your efforts 32and responsible disclosure are greatly appreciated and will be acknowledged. 33 34## Disclosure policy 35 36Here is the security disclosure policy for Node.js 37 38* The security report is received and is assigned a primary handler. This 39 person will coordinate the fix and release process. The problem is confirmed 40 and a list of all affected versions is determined. Code is audited to find 41 any potential similar problems. Fixes are prepared for all releases which are 42 still under maintenance. These fixes are not committed to the public 43 repository but rather held locally pending the announcement. 44 45* A suggested embargo date for this vulnerability is chosen and a CVE (Common 46 Vulnerabilities and Exposures (CVE®)) is requested for the vulnerability. 47 48* On the embargo date, the Node.js security mailing list is sent a copy of the 49 announcement. The changes are pushed to the public repository and new builds 50 are deployed to nodejs.org. Within 6 hours of the mailing list being 51 notified, a copy of the advisory will be published on the Node.js blog. 52 53* Typically the embargo date will be set 72 hours from the time the CVE is 54 issued. However, this may vary depending on the severity of the bug or 55 difficulty in applying a fix. 56 57* This process can take some time, especially when coordination is required 58 with maintainers of other projects. Every effort will be made to handle the 59 bug in as timely a manner as possible; however, it’s important that we follow 60 the release process above to ensure that the disclosure is handled in a 61 consistent manner. 62 63## Receiving security updates 64 65Security notifications will be distributed via the following methods. 66 67* <https://groups.google.com/group/nodejs-sec> 68* <https://nodejs.org/en/blog/> 69 70## Comments on this policy 71 72If you have suggestions on how this process could be improved please submit a 73[pull request](https://github.com/nodejs/nodejs.org) or 74[file an issue](https://github.com/nodejs/security-wg/issues/new) to discuss. 75