Skip to content

Commit

Permalink
doc: add procedure when CVEs don't get published
Browse files Browse the repository at this point in the history
This was the workaround provided by HackerOne team
  • Loading branch information
RafaelGSS authored Nov 27, 2023
1 parent d42949e commit 73b63f4
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions doc/contributing/security-release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -200,6 +200,11 @@ out a better way, forward the email you receive to
* Request publication of [H1 CVE requests][]
* (Check that the "Version Fixed" field in the CVE is correct, and provide
links to the release blogs in the "Public Reference" section)
* In case the reporter doesn't accept the disclosure follow this process:
* Remove the original report reference within the reference text box and
insert the public URL you would like to be attached to this CVE.
* Then uncheck the Public Disclosure on HackerOne box at the bottom of the page.
![image (4)](https://github.com/RafaelGSS/node/assets/26234614/98009250-c538-4e36-895f-6d2cde4cb5c1)

* [ ] PR machine-readable JSON descriptions of the vulnerabilities to the
[core](https://github.com/nodejs/security-wg/tree/HEAD/vuln/core)
Expand Down

0 comments on commit 73b63f4

Please sign in to comment.