@@ -18,17 +18,17 @@ of contact points. Email aliases have been setup for these as follows:
1818
1919* ** Public contact points** . Email address to which people will be directed
2020 by Mitre when they are asked for a way to contact the Node.js team about
21- CVE-related issues.
** [email protected] ** 21+ CVE-related issues.
** [ [email protected] ] [ ] ** 2222
2323* ** Private contact points** . Administrative contacts that Mitre can reach out
2424 to directly in case there are issues that require immediate attention.
25- 25+ 2626
2727* ** Email addresses to add to the CNA email discussion list** . This address has
2828 been added to a closed mailing list that is used for announcements,
2929 sharing documents, or discussion relevant to the CNA community.
3030 The list rarely has more than ten messages a week.
31- 31+ 3232
3333## CNA management processes
3434
@@ -72,7 +72,7 @@ of CVEs should then be requested using the steps listed above.
7272
7373### External CVE request process
7474
75- When a request for a CVE is received via the
[email protected] 75+ When a request for a CVE is received via the
[ [email protected] ] [ ] 7676email alias the following process will be followed (likely updated
7777after we get HackerOne up and running).
7878
@@ -135,3 +135,7 @@ following steps are used to assign, announce and report a CVE.
135135* Move the CVE from the Pending section to the Announced section along
136136 with a link to the Node.js blog post announcing that releases
137137 are available.
138+
139+ 140+ 141+
0 commit comments