vuln/core: fix bad refs

vuln/core/62.json

@@ -14,7 +14,7 @@
   "publish_date": "2019-08-15",
   "author": "Sam Roberts",
   "reported_by": "Jonathan Looney, Piotr Sikora",
-  "ref": "https://nodejs.org/en/blog/vulnerability/august-2019-security-releases/",
+  "ref": "https://nodejs.org/en/blog/vulnerability/aug-2019-security-releases/",
   "type": "CWE-400: Uncontrolled Resource Consumption / Denial of Service",
   "overview": "Netflix has discovered several resource exhaustion vectors affecting a variety of third-party HTTP/2 implementations. These attack vectors can be used to launch DoS attacks against servers that support HTTP/2 communication. Netflix worked with Google and CERT/CC to coordinate disclosure to the Internet community.",
   "affectedEnvironments": ["all"]

vuln/core/84.json

@@ -2,7 +2,7 @@
   "cve": ["CVE-2021-22931"],
   "vulnerable": "12.x || 14.x || 16.x",
   "patched": "^12.22.5 || ^14.17.5 || ^16.6.2",
-  "ref": "https://https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
+  "ref": "https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
   "overview": "Node.js was vulnerable to Remote Code Execution, XSS, application crashes due to missing input validation of host names returned by Domain Name Servers in the Node.js DNS library which can lead to output of wrong hostnames (leading to Domain Hijacking) and injection vulnerabilities in applications using the library. You can read more about it in: https://nvd.nist.gov/vuln/detail/CVE-2021-22931",
   "affectedEnvironments": ["all"]
 }

vuln/core/85.json

@@ -2,7 +2,7 @@
   "cve": ["CVE-2021-22940"],
   "vulnerable": "12.x || 14.x || 16.x",
   "patched": "^12.22.5 || ^14.17.5 || ^16.6.2",
-  "ref": "https://https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
+  "ref": "https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
   "overview": "Node.js was vulnerable to a use after free attack where an attacker might be able to exploit memory corruption to change process behavior. The issue is a follow on to CVE-2021-22930 as the issue was not completely resolved in the fix for CVE-2021-22930. You can read more about it in: https://nvd.nist.gov/vuln/detail/CVE-2021-22940",
   "affectedEnvironments": ["all"]
 }

vuln/core/86.json

@@ -2,7 +2,7 @@
   "cve": ["CVE-2021-22939"],
   "vulnerable": "12.x || 14.x || 16.x",
   "patched": "^12.22.5 || ^14.17.5 || ^16.6.2",
-  "ref": "https://https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
+  "ref": "https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
   "overview": "If the Node.js https API was used incorrectly and \"undefined\" was in passed for the \"rejectUnauthorized\" parameter, no error was returned and connections to servers with an expired certificate would have been accepted. You can read more about it in: https://nvd.nist.gov/vuln/detail/CVE-2021-22939",
   "affectedEnvironments": ["all"]
 }

vuln/core/index.json

@@ -785,7 +785,7 @@
     "publish_date": "2019-08-15",
     "author": "Sam Roberts",
     "reported_by": "Jonathan Looney, Piotr Sikora",
-    "ref": "https://nodejs.org/en/blog/vulnerability/august-2019-security-releases/",
+    "ref": "https://nodejs.org/en/blog/vulnerability/aug-2019-security-releases/",
     "type": "CWE-400: Uncontrolled Resource Consumption / Denial of Service",
     "overview": "Netflix has discovered several resource exhaustion vectors affecting a variety of third-party HTTP/2 implementations. These attack vectors can be used to launch DoS attacks against servers that support HTTP/2 communication. Netflix worked with Google and CERT/CC to coordinate disclosure to the Internet community.",
     "affectedEnvironments": [
@@ -1056,7 +1056,7 @@
     ],
     "vulnerable": "12.x || 14.x || 16.x",
     "patched": "^12.22.5 || ^14.17.5 || ^16.6.2",
-    "ref": "https://https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
+    "ref": "https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
     "overview": "Node.js was vulnerable to Remote Code Execution, XSS, application crashes due to missing input validation of host names returned by Domain Name Servers in the Node.js DNS library which can lead to output of wrong hostnames (leading to Domain Hijacking) and injection vulnerabilities in applications using the library. You can read more about it in: https://nvd.nist.gov/vuln/detail/CVE-2021-22931",
     "affectedEnvironments": [
       "all"
@@ -1068,7 +1068,7 @@
     ],
     "vulnerable": "12.x || 14.x || 16.x",
     "patched": "^12.22.5 || ^14.17.5 || ^16.6.2",
-    "ref": "https://https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
+    "ref": "https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
     "overview": "Node.js was vulnerable to a use after free attack where an attacker might be able to exploit memory corruption to change process behavior. The issue is a follow on to CVE-2021-22930 as the issue was not completely resolved in the fix for CVE-2021-22930. You can read more about it in: https://nvd.nist.gov/vuln/detail/CVE-2021-22940",
     "affectedEnvironments": [
       "all"
@@ -1080,7 +1080,7 @@
     ],
     "vulnerable": "12.x || 14.x || 16.x",
     "patched": "^12.22.5 || ^14.17.5 || ^16.6.2",
-    "ref": "https://https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
+    "ref": "https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/",
     "overview": "If the Node.js https API was used incorrectly and \"undefined\" was in passed for the \"rejectUnauthorized\" parameter, no error was returned and connections to servers with an expired certificate would have been accepted. You can read more about it in: https://nvd.nist.gov/vuln/detail/CVE-2021-22939",
     "affectedEnvironments": [
       "all"