From baffee5b0eef4f1f5dfddef5106ca72bd932ce4d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C3=ABl=20Zasso?= Date: Mon, 4 Oct 2021 11:56:45 +0200 Subject: [PATCH] Blog: fix CVE-2021-22940 references Refs: https://github.com/nodejs/node/issues/40306 --- locale/en/blog/release/v12.22.5.md | 4 ++-- locale/en/blog/release/v14.17.5.md | 4 ++-- locale/en/blog/release/v16.6.2.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/locale/en/blog/release/v12.22.5.md b/locale/en/blog/release/v12.22.5.md index 3ad1b12cc0152..56fd38a14dd61 100644 --- a/locale/en/blog/release/v12.22.5.md +++ b/locale/en/blog/release/v12.22.5.md @@ -12,8 +12,8 @@ author: Bethany Nicolle Griggs * **CVE-2021-3672/CVE-2021-22931**: Improper handling of untypical characters in domain names (High) * Node.js was vulnerable to Remote Code Execution, XSS, application crashes due to missing input validation of hostnames returned by Domain Name Servers in the Node.js DNS library which can lead to the output of wrong hostnames (leading to Domain Hijacking) and injection vulnerabilities in applications using the library. You can read more about it at https://nvd.nist.gov/vuln/detail/CVE-2021-22931. -* **CVE-2021-22930**: Use after free on close http2 on stream canceling (High) - * Node.js was vulnerable to a use after free attack where an attacker might be able to exploit memory corruption to change process behavior. This release includes a follow-up fix for CVE-2021-22930 as the issue was not completely resolved by the previous fix. You can read more about it at https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22930. +* **CVE-2021-22940**: Use after free on close http2 on stream canceling (High) + * Node.js was vulnerable to a use after free attack where an attacker might be able to exploit memory corruption to change process behavior. This release includes a follow-up fix for CVE-2021-22930 as the issue was not completely resolved by the previous fix. You can read more about it at https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22940. * **CVE-2021-22939**: Incomplete validation of rejectUnauthorized parameter (Low) * 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 at https://nvd.nist.gov/vuln/detail/CVE-2021-22939. diff --git a/locale/en/blog/release/v14.17.5.md b/locale/en/blog/release/v14.17.5.md index 61157a3523197..4d084298ffdcd 100644 --- a/locale/en/blog/release/v14.17.5.md +++ b/locale/en/blog/release/v14.17.5.md @@ -12,8 +12,8 @@ author: Bethany Nicolle Griggs * **CVE-2021-3672/CVE-2021-22931**: Improper handling of untypical characters in domain names (High) * Node.js was vulnerable to Remote Code Execution, XSS, application crashes due to missing input validation of hostnames returned by Domain Name Servers in the Node.js DNS library which can lead to the output of wrong hostnames (leading to Domain Hijacking) and injection vulnerabilities in applications using the library. You can read more about it at https://nvd.nist.gov/vuln/detail/CVE-2021-22931. -* **CVE-2021-22930**: Use after free on close http2 on stream canceling (High) - * Node.js was vulnerable to a use after free attack where an attacker might be able to exploit memory corruption to change process behavior. This release includes a follow-up fix for CVE-2021-22930 as the issue was not completely resolved by the previous fix. You can read more about it at https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22930. +* **CVE-2021-22940**: Use after free on close http2 on stream canceling (High) + * Node.js was vulnerable to a use after free attack where an attacker might be able to exploit memory corruption to change process behavior. This release includes a follow-up fix for CVE-2021-22930 as the issue was not completely resolved by the previous fix. You can read more about it at https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22940. * **CVE-2021-22939**: Incomplete validation of rejectUnauthorized parameter (Low) * 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 at https://nvd.nist.gov/vuln/detail/CVE-2021-22939. diff --git a/locale/en/blog/release/v16.6.2.md b/locale/en/blog/release/v16.6.2.md index d85ee0e2ba1bf..f686fcbbdcc9f 100644 --- a/locale/en/blog/release/v16.6.2.md +++ b/locale/en/blog/release/v16.6.2.md @@ -12,8 +12,8 @@ author: Bethany Nicolle Griggs * **CVE-2021-3672/CVE-2021-22931**: Improper handling of untypical characters in domain names (High) * Node.js was vulnerable to Remote Code Execution, XSS, application crashes due to missing input validation of hostnames returned by Domain Name Servers in the Node.js DNS library which can lead to the output of wrong hostnames (leading to Domain Hijacking) and injection vulnerabilities in applications using the library. You can read more about it at https://nvd.nist.gov/vuln/detail/CVE-2021-22931. -* **CVE-2021-22930**: Use after free on close http2 on stream canceling (High) - * Node.js was vulnerable to a use after free attack where an attacker might be able to exploit memory corruption to change process behavior. This release includes a follow-up fix for CVE-2021-22930 as the issue was not completely resolved by the previous fix. You can read more about it at https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22930. +* **CVE-2021-22940**: Use after free on close http2 on stream canceling (High) + * Node.js was vulnerable to a use after free attack where an attacker might be able to exploit memory corruption to change process behavior. This release includes a follow-up fix for CVE-2021-22930 as the issue was not completely resolved by the previous fix. You can read more about it at https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22940. * **CVE-2021-22939**: Incomplete validation of rejectUnauthorized parameter (Low) * 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 at https://nvd.nist.gov/vuln/detail/CVE-2021-22939.