Skip to content

Commit 3ff00e1

Browse files
RafaelGSSrichardlau
authored andcommitted
doc: add procedure when CVEs don't get published
This was the workaround provided by HackerOne team PR-URL: #50945 Refs: nodejs/security-wg#1058 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Tobias Nießen <[email protected]>
1 parent 8a08275 commit 3ff00e1

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

doc/contributing/security-release-process.md

+6
Original file line numberDiff line numberDiff line change
@@ -200,6 +200,12 @@ out a better way, forward the email you receive to
200200
* Request publication of [H1 CVE requests][]
201201
* (Check that the "Version Fixed" field in the CVE is correct, and provide
202202
links to the release blogs in the "Public Reference" section)
203+
* In case the reporter doesn't accept the disclosure follow this process:
204+
* Remove the original report reference within the reference text box and
205+
insert the public URL you would like to be attached to this CVE.
206+
* Then uncheck the Public Disclosure on HackerOne box at the bottom of the
207+
page.
208+
![screenshot of HackerOne CVE form](https://github.com/nodejs/node/assets/26234614/e22e4f33-7948-4dd2-952e-2f9166f5568d)
203209

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

0 commit comments

Comments
 (0)