Описание
ELSA-2022-4796: nodejs:16 security update (IMPORTANT)
nodejs [1:16.14.0-4]
- Apply lock file validation fixes
- Resolves CVE-2021-43616
- Resolves: RHBZ#2070012
Обновленные пакеты
Oracle Linux 8
Oracle Linux aarch64
Module nodejs:16 is enabled
nodejs
16.14.0-4.module+el8.6.0+20672+19f3909b
nodejs-devel
16.14.0-4.module+el8.6.0+20672+19f3909b
nodejs-docs
16.14.0-4.module+el8.6.0+20672+19f3909b
nodejs-full-i18n
16.14.0-4.module+el8.6.0+20672+19f3909b
nodejs-nodemon
2.0.15-1.module+el8.6.0+20672+19f3909b
nodejs-packaging
25-1.module+el8.5.0+20388+4b61e68d
npm
8.3.1-1.16.14.0.4.module+el8.6.0+20672+19f3909b
Oracle Linux x86_64
Module nodejs:16 is enabled
nodejs
16.14.0-4.module+el8.6.0+20672+19f3909b
nodejs-devel
16.14.0-4.module+el8.6.0+20672+19f3909b
nodejs-docs
16.14.0-4.module+el8.6.0+20672+19f3909b
nodejs-full-i18n
16.14.0-4.module+el8.6.0+20672+19f3909b
nodejs-nodemon
2.0.15-1.module+el8.6.0+20672+19f3909b
nodejs-packaging
25-1.module+el8.5.0+20388+4b61e68d
npm
8.3.1-1.16.14.0.4.module+el8.6.0+20672+19f3909b
Связанные CVE
Связанные уязвимости
The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json differs from package.json. This behavior is inconsistent with the documentation, and makes it easier for attackers to install malware that was supposed to have been blocked by an exact version match requirement in package-lock.json. NOTE: The npm team believes this is not a vulnerability. It would require someone to socially engineer package.json which has different dependencies than package-lock.json. That user would have to have file system or write access to change dependencies. The npm team states preventing malicious actors from socially engineering or gaining file system access is outside the scope of the npm CLI.
The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json differs from package.json. This behavior is inconsistent with the documentation, and makes it easier for attackers to install malware that was supposed to have been blocked by an exact version match requirement in package-lock.json. NOTE: The npm team believes this is not a vulnerability. It would require someone to socially engineer package.json which has different dependencies than package-lock.json. That user would have to have file system or write access to change dependencies. The npm team states preventing malicious actors from socially engineering or gaining file system access is outside the scope of the npm CLI.
The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json differs from package.json. This behavior is inconsistent with the documentation, and makes it easier for attackers to install malware that was supposed to have been blocked by an exact version match requirement in package-lock.json. NOTE: The npm team believes this is not a vulnerability. It would require someone to socially engineer package.json which has different dependencies than package-lock.json. That user would have to have file system or write access to change dependencies. The npm team states preventing malicious actors from socially engineering or gaining file system access is outside the scope of the npm CLI.
The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an i ...
