{"id":"CVE-2023-30585","aliases":["BELL-CVE-2023-30585","BIT-node-2023-30585","BIT-node-min-2023-30585","EUVD-2023-34966","GHSA-4r2r-cf85-vmc7","MGASA-2023-0226","SUSE-SU-2023:2655-1","SUSE-SU-2023:2662-1","SUSE-SU-2023:2663-1","SUSE-SU-2023:2669-1","SUSE-SU-2023:2861-1","openSUSE-SU-2024:13021-1"],"status":"published","title":"A vulnerability has been identified in the Node.js (.msi version) installation process,...","description":"A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the \"msiexec.exe\" process, running under the NT AUTHORITY\\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user's registry.\n\nThe issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the \"msiexec.exe\" process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.\n\nThe severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or \"non-privileged\") users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged \"msiexec.exe\" process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.\n\nIt is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.01467,"percentile":0.74041,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2023-06-27T11:05:33Z","modified":"2026-10-28T02:31:08Z","fixes":[{"ecosystem":"Bitnami","package":"node","fixed_in":["16.20.1","18.16.1","20.3.1"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"node-min","fixed_in":["16.20.1","18.16.1","20.3.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Bitnami","package":"node","ranges":[{"type":"SEMVER","events":[{"introduced":"16.0.0"},{"fixed":"16.20.1"},{"introduced":"18.0.0"},{"fixed":"18.16.1"},{"introduced":"20.0.0"},{"fixed":"20.3.1"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"node-min","ranges":[{"type":"SEMVER","events":[{"introduced":"16.0.0"},{"fixed":"16.20.1"},{"introduced":"18.0.0"},{"fixed":"18.16.1"},{"introduced":"20.0.0"},{"fixed":"20.3.1"}]}]},{"source":"osv","ecosystem":"Mageia:8","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.16.1-1.mga8"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 12","package":"nodejs16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.20.1-8.30.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 12","package":"nodejs18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.16.1-8.9.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 15 SP4","package":"nodejs16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.20.1-150400.3.21.1"}]}],"bundled":9},{"source":"osv","ecosystem":"openSUSE:Leap 15.4","package":"nodejs16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.20.1-150400.3.21.1"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 15 SP4","package":"nodejs18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.16.1-150400.9.9.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 15 SP5","package":"nodejs18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.16.1-150400.9.9.1"}]}],"bundled":10},{"source":"osv","ecosystem":"openSUSE:Leap 15.4","package":"nodejs18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.16.1-150400.9.9.1"}]}],"bundled":10},{"source":"osv","ecosystem":"openSUSE:Leap 15.5","package":"nodejs18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.16.1-150400.9.9.1"}]}],"bundled":10},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS","package":"nodejs16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.20.1-150300.7.24.2"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS","package":"nodejs16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.20.1-150300.7.24.2"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP3-LTSS","package":"nodejs16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.20.1-150300.7.24.2"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP3","package":"nodejs16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.20.1-150300.7.24.2"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Manager Server 4.2","package":"nodejs16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.20.1-150300.7.24.2"}]}],"bundled":9},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 7.1","package":"nodejs16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.20.1-150300.7.24.2"}]}],"bundled":9},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"nodejs20","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.3.1-1.1"}]}],"bundled":10}],"products":[{"vendor":"nodejs","product":"node"},{"vendor":"nodejs","product":"node.js"}],"references":[{"url":"https://nodejs.org/en/blog/vulnerability/june-2023-security-releases","tags":["x_transferred","Vendor Advisory","advisory","article"]},{"url":"https://security.netapp.com/advisory/ntap-20241101-0011/","tags":["web","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-30585","tags":["web","advisory"]},{"url":"https://security.netapp.com/advisory/ntap-20241101-0011"},{"url":"https://github.com/advisories/GHSA-4r2r-cf85-vmc7"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2023-30585","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/30xxx/CVE-2023-30585.json","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2023-0226.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=32047","tags":["report"]},{"url":"https://github.com/nodejs/node/releases/tag/v18.16.1","tags":["web"]},{"url":"https://nodejs.org/en/blog/vulnerability/june-2023-security-releases/","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20232655-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1211407","tags":["report"]},{"url":"https://bugzilla.suse.com/1211604","tags":["report"]},{"url":"https://bugzilla.suse.com/1211605","tags":["report"]},{"url":"https://bugzilla.suse.com/1211606","tags":["report"]},{"url":"https://bugzilla.suse.com/1211607","tags":["report"]},{"url":"https://bugzilla.suse.com/1212574","tags":["report"]},{"url":"https://bugzilla.suse.com/1212579","tags":["report"]},{"url":"https://bugzilla.suse.com/1212581","tags":["report"]},{"url":"https://bugzilla.suse.com/1212582","tags":["report"]},{"url":"https://bugzilla.suse.com/1212583","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-30581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-30585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-30588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-30589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-30590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-31124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-31130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-31147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-32067","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20232662-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1208744","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-25881","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20232663-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20232669-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2023/suse-su-20232861-1/","tags":["advisory"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2023-30582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-30583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-30584","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-30586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-30587","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2023-30585","description":"A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the \"msiexec.exe\" process, running under the NT AUTHORITY\\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user's registry.\n\nThe issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the \"msiexec.exe\" process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.\n\nThe severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or \"non-privileged\") users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged \"msiexec.exe\" process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.\n\nIt is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.","status":"published","published":"2023-11-28T01:23:08.734Z","modified":"2026-10-08T21:13:54.831Z","updated_at":"2026-11-02T14:35:22.640346Z"}],"euvd":[{"id":"EUVD-2023-34966","description":"A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the \"msiexec.exe\" process, running under the NT AUTHORITY\\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user's registry.\n\nThe issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the \"msiexec.exe\" process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.\n\nThe severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or \"non-privileged\") users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged \"msiexec.exe\" process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.\n\nIt is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.","status":"published","published":"2023-11-28T01:23:08Z","modified":"2026-10-08T21:13:54Z","updated_at":"2026-11-02T17:27:26.452288Z"}],"ghsa":[{"id":"GHSA-4r2r-cf85-vmc7","title":"A vulnerability has been identified in the Node.js (.msi version) installation process,...","description":"A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the \"msiexec.exe\" process, running under the NT AUTHORITY\\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user's registry.\n\nThe issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the \"msiexec.exe\" process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.\n\nThe severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or \"non-privileged\") users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged \"msiexec.exe\" process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.\n\nIt is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.","status":"published","published":"2023-11-28T03:30:21Z","modified":"2025-11-04T00:30:42Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:04:25.970519Z"}],"nvd":[{"id":"CVE-2023-30585","description":"A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the \"msiexec.exe\" process, running under the NT AUTHORITY\\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user's registry.\n\nThe issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the \"msiexec.exe\" process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.\n\nThe severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or \"non-privileged\") users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged \"msiexec.exe\" process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.\n\nIt is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.","status":"published","published":"2023-11-28T02:15:42.077Z","modified":"2026-10-08T22:17:23.563Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high","assessor":"primary"}],"updated_at":"2026-11-02T14:08:49.393375Z"}],"osv":[{"id":"BELL-CVE-2023-30585","title":"CVE-2023-30585 does not affect BellSoft software","status":"withdrawn","published":"2023-10-18T13:45:41.315436Z","modified":"2026-02-18T07:38:27.085914Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","level":"high"}],"updated_at":"2026-11-02T15:28:17.742221Z"},{"id":"BIT-node-2023-30585","description":"A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the \"msiexec.exe\" process, running under the NT AUTHORITY\\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user's registry.\n\nThe issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the \"msiexec.exe\" process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.\n\nThe severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or \"non-privileged\") users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged \"msiexec.exe\" process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.\n\nIt is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.","status":"published","published":"2024-03-06T11:01:27.978Z","modified":"2026-09-08T08:48:17.659057962Z","updated_at":"2026-11-02T15:28:34.007508Z"},{"id":"BIT-node-min-2023-30585","description":"A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the \"msiexec.exe\" process, running under the NT AUTHORITY\\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user's registry.\n\nThe issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the \"msiexec.exe\" process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.\n\nThe severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or \"non-privileged\") users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged \"msiexec.exe\" process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.\n\nIt is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.","status":"published","published":"2024-12-16T13:59:16.424Z","modified":"2026-09-08T08:48:17.38797121Z","updated_at":"2026-11-02T15:28:34.007508Z"},{"id":"CVE-2023-30585","description":"A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install Node.js using the .msi installer. This vulnerability emerges during the repair operation, where the \"msiexec.exe\" process, running under the NT AUTHORITY\\SYSTEM context, attempts to read the %USERPROFILE% environment variable from the current user's registry.\n\nThe issue arises when the path referenced by the %USERPROFILE% environment variable does not exist. In such cases, the \"msiexec.exe\" process attempts to create the specified path in an unsafe manner, potentially leading to the creation of arbitrary folders in arbitrary locations.\n\nThe severity of this vulnerability is heightened by the fact that the %USERPROFILE% environment variable in the Windows registry can be modified by standard (or \"non-privileged\") users. Consequently, unprivileged actors, including malicious entities or trojans, can manipulate the environment variable key to deceive the privileged \"msiexec.exe\" process. This manipulation can result in the creation of folders in unintended and potentially malicious locations.\n\nIt is important to note that this vulnerability is specific to Windows users who install Node.js using the .msi installer. Users who opt for other installation methods are not affected by this particular issue.","status":"published","published":"2023-11-28T01:23:08.734Z","modified":"2026-10-28T02:31:08.42630846Z","updated_at":"2026-11-02T15:44:31.790231Z"},{"id":"MGASA-2023-0226","title":"Updated nodejs packages fix security vulnerability","description":"Current nodejs 14 branch in Mageia 8 is end of life and there are no more\nsecurity updates.\n\nThis release allows to move to the new nodejs 18 LTS branch and fixes the\nfollowing CVEs\nCVE-2023-30581: mainModule.__proto__ Bypass Experimental Policy Mechanism\n(High)\nCVE-2023-30585: Privilege escalation via Malicious Registry Key\nmanipulation during Node.js installer repair process (Medium)\nCVE-2023-30588: Process interuption due to invalid Public Key information\nin x509 certificates (Medium)\nCVE-2023-30589: HTTP Request Smuggling via Empty headers separated by CR\n(Medium)\nCVE-2023-30590: DiffieHellman does not generate keys after setting a\nprivate key (Medium)\nOpenSSL Security Releases\n OpenSSL security advisory 28th March.\n OpenSSL security advisory 20th April.\n OpenSSL security advisory 30th May\nc-ares vulnerabilities:\n GHSA-9g78-jv2r-p7vc\n GHSA-8r8p-23f3-64c2\n GHSA-54xr-f67r-4pc4\n GHSA-x6mf-cxr9-8q6v\n","status":"published","published":"2023-07-07T05:54:45Z","modified":"2026-04-16T04:41:15.683592451Z","updated_at":"2026-11-02T15:49:42.263076Z"},{"id":"openSUSE-SU-2024:13021-1","title":"corepack20-20.3.1-1.1 on GA media","description":"These are all security issues fixed in the corepack20-20.3.1-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T03:42:09.864207Z","updated_at":"2026-11-02T16:58:36.025801Z"},{"id":"SUSE-SU-2023:2655-1","title":"Security update for nodejs16","description":"This update for nodejs16 fixes the following issues:\n\nUpdate to version 16.20.1:\n\n- CVE-2023-30581: Fixed mainModule.__proto__ Bypass Experimental Policy Mechanism (bsc#1212574).\n- CVE-2023-30585: Fixed privilege escalation via Malicious Registry Key manipulation during Node.js installer repair process (bsc#1212579).\n- CVE-2023-30588: Fixed process interuption due to invalid Public Key information in x509 certificates (bsc#1212581).\n- CVE-2023-30589: Fixed HTTP Request Smuggling via empty headers separated by CR (bsc#1212582).\n- CVE-2023-30590: Fixed DiffieHellman key generation after setting a private key (bsc#1212583).\n- CVE-2023-31124: Fixed cross compilation issue with AutoTools that does not set CARES_RANDOM_FILE (bsc#1211607).\n- CVE-2023-31130: Fixed buffer underwrite problem in ares_inet_net_pton() (bsc#1211606).\n- CVE-2023-31147: Fixed insufficient randomness in generation of DNS query IDs (bsc#1211605).\n- CVE-2023-32067: Fixed denial-of-service via 0-byte UDP payload (bsc#1211604).\n\nBug fixes:\n\n- Increased the default timeout on unit tests from 2 to 20 minutes. This seems to have lead to build failures on some platforms, like s390x in Factory. (bsc#1211407)\n","status":"published","published":"2023-06-27T11:05:33Z","modified":"2025-05-02T04:34:54.803426Z","updated_at":"2026-11-02T15:53:53.019382Z"},{"id":"SUSE-SU-2023:2662-1","title":"Security update for nodejs18","description":"This update for nodejs18 fixes the following issues:\n\nUpdate to version 18.16.1:\n\n- CVE-2023-30581: Fixed mainModule.__proto__ Bypass Experimental Policy Mechanism (bsc#1212574).\n- CVE-2023-30585: Fixed privilege escalation via Malicious Registry Key manipulation during Node.js installer repair process (bsc#1212579).\n- CVE-2023-30588: Fixed process interuption due to invalid Public Key information in x509 certificates (bsc#1212581).\n- CVE-2023-30589: Fixed HTTP Request Smuggling via empty headers separated by CR (bsc#1212582).\n- CVE-2023-30590: Fixed DiffieHellman key generation after setting a private key (bsc#1212583).\n- CVE-2023-31124: Fixed cross compilation issue with AutoTools that does not set CARES_RANDOM_FILE (bsc#1211607).\n- CVE-2023-31130: Fixed buffer underwrite problem in ares_inet_net_pton() (bsc#1211606).\n- CVE-2023-31147: Fixed insufficient randomness in generation of DNS query IDs (bsc#1211605).\n- CVE-2023-32067: Fixed denial-of-service via 0-byte UDP payload (bsc#1211604).\n- CVE-2022-25881: Fixed a Regular Expression Denial of Service (bsc#1208744).\n\nBug fixes:\n\n- Increased the default timeout on unit tests from 2 to 20 minutes. This seems to have lead to build failures on some platforms, like s390x in Factory. (bsc#1211407)\n","status":"published","published":"2023-06-27T18:26:44Z","modified":"2025-05-02T04:32:56.41748Z","updated_at":"2026-11-02T15:53:53.019382Z"},{"id":"SUSE-SU-2023:2663-1","title":"Security update for nodejs16","description":"This update for nodejs16 fixes the following issues:\n\nUpdate to version 16.20.1:\n\n- CVE-2023-30581: Fixed mainModule.__proto__ Bypass Experimental Policy Mechanism (bsc#1212574).\n- CVE-2023-30585: Fixed privilege escalation via Malicious Registry Key manipulation during Node.js installer repair process (bsc#1212579).\n- CVE-2023-30588: Fixed process interuption due to invalid Public Key information in x509 certificates (bsc#1212581).\n- CVE-2023-30589: Fixed HTTP Request Smuggling via empty headers separated by CR (bsc#1212582).\n- CVE-2023-30590: Fixed DiffieHellman key generation after setting a private key (bsc#1212583).\n- CVE-2023-31124: Fixed cross compilation issue with AutoTools that does not set CARES_RANDOM_FILE (bsc#1211607).\n- CVE-2023-31130: Fixed buffer underwrite problem in ares_inet_net_pton() (bsc#1211606).\n- CVE-2023-31147: Fixed insufficient randomness in generation of DNS query IDs (bsc#1211605).\n- CVE-2023-32067: Fixed denial-of-service via 0-byte UDP payload (bsc#1211604).\n    \nBug fixes:\n\n- Increased the default timeout on unit tests from 2 to 20 minutes. This seems to have lead to build failures on some platforms, like s390x in Factory. (bsc#1211407)\n","status":"published","published":"2023-06-27T18:27:09Z","modified":"2026-02-04T03:57:22.509724Z","updated_at":"2026-11-02T15:53:53.019382Z"},{"id":"SUSE-SU-2023:2669-1","title":"Security update for nodejs18","description":"This update for nodejs18 fixes the following issues:\n\nUpdate to version 18.16.1:\n\n- CVE-2023-30581: Fixed mainModule.__proto__ Bypass Experimental Policy Mechanism (bsc#1212574).\n- CVE-2023-30585: Fixed privilege escalation via Malicious Registry Key manipulation during Node.js installer repair process (bsc#1212579).\n- CVE-2023-30588: Fixed process interuption due to invalid Public Key information in x509 certificates (bsc#1212581).\n- CVE-2023-30589: Fixed HTTP Request Smuggling via empty headers separated by CR (bsc#1212582).\n- CVE-2023-30590: Fixed DiffieHellman key generation after setting a private key (bsc#1212583).\n- CVE-2023-31124: Fixed cross compilation issue with AutoTools that does not set CARES_RANDOM_FILE (bsc#1211607).\n- CVE-2023-31130: Fixed buffer underwrite problem in ares_inet_net_pton() (bsc#1211606).\n- CVE-2023-31147: Fixed insufficient randomness in generation of DNS query IDs (bsc#1211605).\n- CVE-2023-32067: Fixed denial-of-service via 0-byte UDP payload (bsc#1211604).\n- CVE-2022-25881: Fixed a Regular Expression Denial of Service (bsc#1208744).\n\nBug fixes:\n\n- Increased the default timeout on unit tests from 2 to 20 minutes. This seems to have lead to build failures on some platforms, like s390x in Factory. (bsc#1211407)\n","status":"published","published":"2023-06-28T07:25:15Z","modified":"2026-02-04T02:58:02.435781Z","updated_at":"2026-11-02T15:53:53.019382Z"},{"id":"SUSE-SU-2023:2861-1","title":"Security update for nodejs16","description":"This update for nodejs16 fixes the following issues:\n\nUpdate to version 16.20.1:\n\n- CVE-2023-30581: Fixed mainModule.__proto__ Bypass Experimental Policy Mechanism (bsc#1212574).\n- CVE-2023-30585: Fixed privilege escalation via Malicious Registry Key manipulation during Node.js installer repair process (bsc#1212579).\n- CVE-2023-30588: Fixed process interuption due to invalid Public Key information in x509 certificates (bsc#1212581).\n- CVE-2023-30589: Fixed HTTP Request Smuggling via empty headers separated by CR (bsc#1212582).\n- CVE-2023-30590: Fixed DiffieHellman key generation after setting a private key (bsc#1212583).\n- CVE-2023-31124: Fixed cross compilation issue with AutoTools that does not set CARES_RANDOM_FILE (bsc#1211607).\n- CVE-2023-31130: Fixed buffer underwrite problem in ares_inet_net_pton() (bsc#1211606).\n- CVE-2023-31147: Fixed insufficient randomness in generation of DNS query IDs (bsc#1211605).\n- CVE-2023-32067: Fixed denial-of-service via 0-byte UDP payload (bsc#1211604).\n    \nBug fixes:\n\n- Increased the default timeout on unit tests from 2 to 20 minutes. This seems to have lead to build failures on some platforms, like s390x in Factory. (bsc#1211407)\n","status":"published","published":"2023-07-17T14:46:32Z","modified":"2026-02-04T03:07:51.476814Z","updated_at":"2026-11-02T15:53:53.019382Z"}]}}