|
1 | 1 | ---
|
2 |
| -date: 2023-02-14T14:00:00.000Z |
| 2 | +date: 2023-02-16T21:00:00.000Z |
3 | 3 | category: vulnerability
|
4 |
| -title: Tuesday February 14 2023 Security Releases |
| 4 | +title: Thursday February 16 2023 Security Releases |
5 | 5 | slug: february-2023-security-releases
|
6 | 6 | layout: blog-post.hbs
|
7 | 7 | author: Michael Dawson
|
8 | 8 | ---
|
9 | 9 |
|
| 10 | +# _(Update 16-February-2023)_ Security releases available |
| 11 | + |
| 12 | +Updates are now available for the v19.x, v18.x, v16.x, and v14.x Node.js release lines for the |
| 13 | +following issues. |
| 14 | + |
| 15 | +## OpenSSL Security updates |
| 16 | + |
| 17 | +This security release includes OpenSSL security updates as outlined in the recent |
| 18 | +[OpenSSL security advisory](https://www.openssl.org/news/secadv/20230207.txt). |
| 19 | + |
| 20 | +Impacts: |
| 21 | + |
| 22 | +* All versions of the 19.x, 18.x, 16.x, and 14.x release lines. |
| 23 | + |
| 24 | +## Node.js Permissions policies can be bypassed via process.mainModule (High) ([CVE-2023-23918](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-23918)) |
| 25 | + |
| 26 | +It was possible to bypass [Permissions](https://nodejs.org/api/permissions.html) and access non authorized modules by using process.mainModule.require(). This only affects users who had enabled the experimental permissions option with --experimental-policy. |
| 27 | + |
| 28 | +Thank you, to [@goums](https://github.com/goums) for reporting this vulnerability and thank you [Rafael Gonzaga](https://github.com/RafaelGSS) for fixing it. |
| 29 | + |
| 30 | +Impacts: |
| 31 | + |
| 32 | +* All versions of the 19.x, 18.x, 16.x, and 14.x release lines. |
| 33 | + |
| 34 | +## Node.js OpenSSL error handling issues in nodejs crypto library (Medium) ([CVE-2023-23919](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-23919)) |
| 35 | + |
| 36 | +In some cases Node.js did does not clear the OpenSSL error stack after operations that may set it. This may lead to false positive errors during subsequent cryptographic operations that happen to be on the same thread. This in turn could be used to cause a denial of service. |
| 37 | + |
| 38 | +"Thank you, to Morgan Jones and Ryan Dorrity from Viasat Secure Mobile for reporting and discovering this vulnerability and thank you [Rafael Gonzaga](https://github.com/RafaelGSS) for fixing it. |
| 39 | + |
| 40 | +Impacts: |
| 41 | + |
| 42 | +* Versions of < 19.2.0 and lower of the 19.x release line and all versions of the 18.x, and 16.x release lines. |
| 43 | + |
| 44 | +## Fetch API in Node.js did not protect against CRLF injection in host headers (Medium) ([CVE-2023-23936](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-23936)) |
| 45 | + |
| 46 | +The [fetch API](https://nodejs.org/dist/latest/docs/api/globals.html#fetch) in Node.js did not prevent |
| 47 | +CRLF injection in the 'host' header potentially allowing attacks such as HTTP response splitting |
| 48 | +and HTTP header injection. |
| 49 | + |
| 50 | +Thank you, to Zhipeng Zhang ([@timon8](https://hackerone.com/timon8)) for reporting this vulnerability and thank you Robert Nagy for fixing it. |
| 51 | + |
| 52 | +Impacts: |
| 53 | + |
| 54 | +* All versions of the 19.x, 18.x and 16.x release lines. |
| 55 | + |
| 56 | +## Regular Expression Denial of Service in Headers in Node.js fetch API(Low) ([CVE-2023-24807](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24807)) |
| 57 | + |
| 58 | +The Headers.set() and Headers.append() methods in the |
| 59 | +[fetch API](https://nodejs.org/dist/latest/docs/api/globals.html#fetch) in Node.js where vulnerable to Regular a Expression Denial of Service (ReDoS) attacks. |
| 60 | + |
| 61 | +Thank you, to Carter Snook for reporting this vulnerability and thank you Rich Trott for fixing it. |
| 62 | + |
| 63 | +Impacts: |
| 64 | + |
| 65 | +* All versions of the 19.x, 18.x, and 16.x release lines. |
| 66 | + |
| 67 | +## Node.js insecure loading of ICU data through ICU_DATA environment variable (Low) ([CVE-2023-23920](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-23920)) |
| 68 | + |
| 69 | +Node.js would search and potentially load ICU data when running with elevated priviledges. Node.js |
| 70 | +was modified to build with ICU_NO_USER_DATA_OVERRIDE to avoid this. |
| 71 | + |
| 72 | +Thank you, to Ben Noordhuis for reporting this vulnerability and thank you [Rafael Gonzaga](https://github.com/RafaelGSS) for fixing it. |
| 73 | + |
| 74 | +Impacts: |
| 75 | + |
| 76 | +* All versions of the 19.x, 18.x, 16.x, and 14.x release lines. |
| 77 | + |
| 78 | +## npm update for Node.js 14 |
| 79 | + |
| 80 | +This security release also includes an npm update for Node.js 14 to address a number |
| 81 | +of CVEs which either do not affect Node.js or are low severity in the context of Node.js. You |
| 82 | +can get more details for the individual CVEs in |
| 83 | +[nodejs-dependency-vuln-assessments](https://github.com/nodejs/nodejs-dependency-vuln-assessments). |
| 84 | + |
| 85 | +Impacts: |
| 86 | + |
| 87 | +* All versions 14.x release lines. |
| 88 | + |
| 89 | +## Downloads and release details |
| 90 | + |
| 91 | +Thanks to Rafael Gonzaga and Richard Lau for their work on the releases. |
| 92 | + |
| 93 | +* [Node.js v14.21.3 (LTS)](https://nodejs.org/en/blog/release/v14.21.3/) |
| 94 | +* [Node.js v16.19.1 (LTS)](https://nodejs.org/en/blog/release/v16.19.1/) |
| 95 | +* [Node.js v18.14.1 (LTS)](https://nodejs.org/en/blog/release/v18.14.1/) |
| 96 | +* [Node.js v19.6.1 (Current)](https://nodejs.org/en/blog/release/v19.6.1/) |
| 97 | + |
10 | 98 | ## _(Update 14-February-2023)_ 2 Day delay in security releases
|
11 | 99 |
|
12 | 100 | The Node.js project is delaying the planned security releases until Thursday
|
|
0 commit comments