nodejs - Debian Package Tracker

general

source: nodejs (main)
version: 18.13.0+dfsg1-1
maintainer: Debian Javascript Maintainers (archive) (DMD)
uploaders: Jonas Smedegaard [DMD] – Jérémy Lal [DMD]
arch: all amd64 arm64 armel armhf i386 kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64 ppc64el s390x
std-ver: 4.6.1.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 10.24.0~dfsg-1~deb10u1
o-o-sec: 10.24.0~dfsg-1~deb10u3
oldstable: 12.22.12~dfsg-1~deb11u4
old-sec: 12.22.12~dfsg-1~deb11u4
stable: 18.13.0+dfsg1-1
testing: 18.13.0+dfsg1-1
unstable: 18.13.0+dfsg1-1

versioned links

10.24.0~dfsg-1~deb10u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
10.24.0~dfsg-1~deb10u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
12.22.12~dfsg-1~deb11u4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
18.13.0+dfsg1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libnode-dev (1 bugs: 0, 1, 0, 0)
libnode108
nodejs (20 bugs: 1, 18, 1, 0)
nodejs-doc

action needed

Problems while searching for a new upstream version high

uscan had problems while searching for a new upstream version:

unknown ctype nodejs

Created: 2021-02-12 Last update: 2023-10-08 02:40

A new upstream version is available: 18.18.0 high

A new upstream version 18.18.0 is available, you should consider packaging it.

Created: 2023-08-17 Last update: 2023-10-08 02:40

10 security issues in trixie high

There are 10 open security issues in trixie.

10 important issues:

CVE-2023-23918: A privilege escalation vulnerability exists in Node.js <19.6.1, <18.14.1, <16.19.1 and <14.21.3 that made it possible to bypass the experimental Permissions (https://nodejs.org/api/permissions.html) feature in Node.js and access non authorized modules by using process.mainModule.require(). This only affects users who had enabled the experimental permissions option with --experimental-policy.
CVE-2023-23919: A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases 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.
CVE-2023-23920: An untrusted search path vulnerability exists in Node.js. <19.6.1, <18.14.1, <16.19.1, and <14.21.3 that could allow an attacker to search and potentially load ICU data when running with elevated privileges.
CVE-2023-30581:
CVE-2023-30588:
CVE-2023-30589: The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20
CVE-2023-30590:
CVE-2023-32002: The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.
CVE-2023-32006: The use of `module.constructor.createRequire()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x, and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.
CVE-2023-32559: A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. The use of the deprecated API `process.binding()` can bypass the policy mechanism by requiring internal modules and eventually take advantage of `process.binding('spawn_sync')` run arbitrary code, outside of the limits defined in a `policy.json` file. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.

Created: 2023-06-11 Last update: 2023-10-07 13:36

10 security issues in sid high

There are 10 open security issues in sid.

10 important issues:

CVE-2023-23918: A privilege escalation vulnerability exists in Node.js <19.6.1, <18.14.1, <16.19.1 and <14.21.3 that made it possible to bypass the experimental Permissions (https://nodejs.org/api/permissions.html) feature in Node.js and access non authorized modules by using process.mainModule.require(). This only affects users who had enabled the experimental permissions option with --experimental-policy.
CVE-2023-23919: A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases 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.
CVE-2023-23920: An untrusted search path vulnerability exists in Node.js. <19.6.1, <18.14.1, <16.19.1, and <14.21.3 that could allow an attacker to search and potentially load ICU data when running with elevated privileges.
CVE-2023-30581:
CVE-2023-30588:
CVE-2023-30589: The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20
CVE-2023-30590:
CVE-2023-32002: The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.
CVE-2023-32006: The use of `module.constructor.createRequire()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x, and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.
CVE-2023-32559: A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. The use of the deprecated API `process.binding()` can bypass the policy mechanism by requiring internal modules and eventually take advantage of `process.binding('spawn_sync')` run arbitrary code, outside of the limits defined in a `policy.json` file. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.

Created: 2023-02-23 Last update: 2023-10-07 13:36

7 security issues in bullseye high

There are 7 open security issues in bullseye.

7 important issues:

CVE-2023-30581:
CVE-2023-30588:
CVE-2023-30589: The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20
CVE-2023-30590:
CVE-2023-32002: The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.
CVE-2023-32006: The use of `module.constructor.createRequire()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x, and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.
CVE-2023-32559: A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. The use of the deprecated API `process.binding()` can bypass the policy mechanism by requiring internal modules and eventually take advantage of `process.binding('spawn_sync')` run arbitrary code, outside of the limits defined in a `policy.json` file. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.

Created: 2023-06-21 Last update: 2023-10-07 13:36

10 security issues in bookworm high

There are 10 open security issues in bookworm.

7 important issues:

CVE-2023-30581:
CVE-2023-30588:
CVE-2023-30589: The llhttp parser in the http module in Node v20.2.0 does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS). The CR character (without LF) is sufficient to delimit HTTP header fields in the llhttp parser. According to RFC7230 section 3, only the CRLF sequence should delimit each header-field. This impacts all Node.js active versions: v16, v18, and, v20
CVE-2023-30590:
CVE-2023-32002: The use of `Module._load()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.
CVE-2023-32006: The use of `module.constructor.createRequire()` can bypass the policy mechanism and require modules outside of the policy.json definition for a given module. This vulnerability affects all users using the experimental policy mechanism in all active release lines: 16.x, 18.x, and, 20.x. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.
CVE-2023-32559: A privilege escalation vulnerability exists in the experimental policy mechanism in all active release lines: 16.x, 18.x and, 20.x. The use of the deprecated API `process.binding()` can bypass the policy mechanism by requiring internal modules and eventually take advantage of `process.binding('spawn_sync')` run arbitrary code, outside of the limits defined in a `policy.json` file. Please note that at the time this CVE was issued, the policy is an experimental feature of Node.js.

3 issues left for the package maintainer to handle:

CVE-2023-23918: (postponed; to be fixed through a stable update) A privilege escalation vulnerability exists in Node.js <19.6.1, <18.14.1, <16.19.1 and <14.21.3 that made it possible to bypass the experimental Permissions (https://nodejs.org/api/permissions.html) feature in Node.js and access non authorized modules by using process.mainModule.require(). This only affects users who had enabled the experimental permissions option with --experimental-policy.
CVE-2023-23919: (postponed; to be fixed through a stable update) A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases 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.
CVE-2023-23920: (postponed; to be fixed through a stable update) An untrusted search path vulnerability exists in Node.js. <19.6.1, <18.14.1, <16.19.1, and <14.21.3 that could allow an attacker to search and potentially load ICU data when running with elevated privileges.

You can find information about how to handle these issues in the security team's documentation.

Created: 2023-06-10 Last update: 2023-10-07 13:36

lintian reports 9 errors and 6 warnings high

Lintian reports 9 errors and 6 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2023-01-12 Last update: 2023-09-03 06:05

debian/patches: 3 patches with invalid metadata, 2 patches to forward upstream high

Among the 23 debian patches available in version 18.13.0+dfsg1-1 of the package, we noticed the following issues:

3 patches with invalid metadata that ought to be fixed.
2 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2023-02-27 20:59

Failed to analyze the VCS repository. Please troubleshoot and fix the issue. high

vcswatch reports that there is an error with this package's VCS, or the debian/changelog file inside it. Please check the error shown below and try to fix it. You might have to update the VCS URL in the debian/control file to point to the correct repository.

Repository size 2699792384 exceeds 1 GiB, blocking it

Created: 2022-06-15 Last update: 2023-01-22 18:07

3 bugs tagged patch in the BTS normal

The BTS contains patches fixing 3 bugs, consider including or untagging them.

Created: 2023-09-13 Last update: 2023-10-08 02:33

Fails to build during reproducibility testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2022-04-04 Last update: 2023-10-07 22:01

Build log checks report 2 warnings low

Build log checks report 2 warnings

Created: 2022-11-09 Last update: 2023-01-12 07:37

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.6.2 instead of 4.6.1.0).

Created: 2022-12-17 Last update: 2023-01-12 02:39

testing migrations

This package will soon be part of the auto-icu transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.

news

[rss feed]

[2023-05-06] Accepted nodejs 12.22.12~dfsg-1~deb11u4 (source) into proposed-updates (Debian FTP Masters) (signed by: Aron Xu)
[2023-05-02] Accepted nodejs 12.22.12~dfsg-1~deb11u4 (source) into stable-security (Debian FTP Masters) (signed by: Aron Xu)
[2023-02-25] Accepted nodejs 10.24.0~dfsg-1~deb10u3 (source) into oldstable (Guilhem Moulin)
[2023-02-18] Accepted nodejs 12.22.12~dfsg-1~deb11u3 (source) into proposed-updates (Debian FTP Masters) (signed by: Aron Xu)
[2023-02-18] Accepted nodejs 12.22.12~dfsg-1~deb11u2 (source) into proposed-updates (Debian FTP Masters) (signed by: Aron Xu)
[2023-02-18] Accepted nodejs 12.22.12~dfsg-1~deb11u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Jérémy Lal)
[2023-01-24] Accepted nodejs 12.22.12~dfsg-1~deb11u3 (source) into stable-security (Debian FTP Masters) (signed by: Aron Xu)
[2023-01-24] Accepted nodejs 12.22.12~dfsg-1~deb11u2 (source) into stable-security (Debian FTP Masters) (signed by: Aron Xu)
[2023-01-17] nodejs 18.13.0+dfsg1-1 MIGRATED to testing (Debian testing watch)
[2023-01-11] Accepted nodejs 18.13.0+dfsg1-1 (source) into unstable (Jérémy Lal)
[2023-01-11] nodejs 18.13.0+dfsg-1 MIGRATED to testing (Debian testing watch)
[2023-01-06] Accepted nodejs 18.13.0+dfsg-1 (source) into unstable (Jérémy Lal)
[2022-11-19] nodejs 18.12.1+dfsg-2 MIGRATED to testing (Debian testing watch)
[2022-11-09] Accepted nodejs 18.12.1+dfsg-2 (source) into unstable (Jérémy Lal)
[2022-11-05] Accepted nodejs 18.12.1+dfsg-1 (source) into unstable (Jérémy Lal)
[2022-10-27] Accepted nodejs 18.12.0+dfsg-1 (source) into unstable (Jérémy Lal)
[2022-10-26] Accepted nodejs 18.11.0+dfsg-4 (source) into experimental (Jérémy Lal)
[2022-10-18] Accepted nodejs 18.11.0+dfsg-3 (source) into experimental (Jérémy Lal) (signed by: Xavier Guimard)
[2022-10-16] nodejs 18.10.0+dfsg-6 MIGRATED to testing (Debian testing watch)
[2022-10-14] Accepted nodejs 18.11.0+dfsg-2 (source) into experimental (Jérémy Lal)
[2022-10-14] Accepted nodejs 18.11.0+dfsg-1 (source) into experimental (Jérémy Lal)
[2022-10-10] Accepted nodejs 18.10.0+dfsg-6 (source) into unstable (Jérémy Lal)
[2022-10-09] Accepted nodejs 18.10.0+dfsg-5 (source) into unstable (Jérémy Lal)
[2022-10-05] Accepted nodejs 10.24.0~dfsg-1~deb10u2 (source) into oldstable (Sylvain Beucler)
[2022-10-01] Accepted nodejs 18.10.0+dfsg-4 (source) into unstable (Jérémy Lal)
[2022-09-29] Accepted nodejs 18.10.0+dfsg-3 (source) into unstable (Jérémy Lal)
[2022-09-29] Accepted nodejs 18.10.0+dfsg-2 (source) into unstable (Jérémy Lal)
[2022-09-29] Accepted nodejs 18.10.0+dfsg-1 (source) into unstable (Jérémy Lal)
[2022-09-06] nodejs 18.7.0+dfsg-5 MIGRATED to testing (Debian testing watch)
[2022-09-04] Accepted nodejs 18.8.0+dfsg-1 (source) into experimental (Jérémy Lal)

bugs [bug history graph]

all: 29 30
RC: 3
I&N: 24 25
M&W: 1
F&P: 1
patch: 3

links

homepage
lintian (9, 6)
buildd: logs, checks, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 18.13.0+dfsg1-1ubuntu2
40 bugs
patches for 18.13.0+dfsg1-1ubuntu2