Описание
ELSA-2025-7433: nodejs:22 security update (IMPORTANT)
nodejs [1:22.15.0-1]
- Update to 22.15.0
- Drop upstream patches Resolves: RHEL-87319 RHEL-86586
[1:22.13.1-4]
- Patch fix for sqlite CVE-2025-31498 Resolves: RHEL-87319
[1:22.13.1-3]
- Update c-ares to newest version with fix for CVE-2025-31498 Resolves: RHEL-86586
[1:22.13.1-2]
- Remove obsolete lua pretransaction script from spec file Resolves: RHEL-81119
- Disable npm update notifications for users Resolves: RHEL-81158
[1:22.13.1-1]
- Update to version 22.13.1 Fixes CVE-2025-23083 CVE-2025-23085 CVE-2025-22150 Resolves: RHEL-76354
[1:22.11.0-1]
- Update to version 22.11.0
[22.4.1-4]
- Initial import of nodeJS 22
nodejs-nodemon nodejs-packaging
Обновленные пакеты
Oracle Linux 9
Oracle Linux aarch64
Module nodejs:22 is enabled
nodejs
22.15.0-1.module+el9.6.0+90588+1a9ecb62
nodejs-devel
22.15.0-1.module+el9.6.0+90588+1a9ecb62
nodejs-docs
22.15.0-1.module+el9.6.0+90588+1a9ecb62
nodejs-full-i18n
22.15.0-1.module+el9.6.0+90588+1a9ecb62
nodejs-libs
22.15.0-1.module+el9.6.0+90588+1a9ecb62
nodejs-nodemon
3.0.1-1.module+el9.6.0+90588+1a9ecb62
nodejs-packaging
2021.06-4.module+el9.6.0+90588+1a9ecb62
nodejs-packaging-bundler
2021.06-4.module+el9.6.0+90588+1a9ecb62
npm
10.9.2-1.22.15.0.1.module+el9.6.0+90588+1a9ecb62
v8-12.4-devel
12.4.254.21-1.22.15.0.1.module+el9.6.0+90588+1a9ecb62
Oracle Linux x86_64
Module nodejs:22 is enabled
nodejs
22.15.0-1.module+el9.6.0+90588+1a9ecb62
nodejs-devel
22.15.0-1.module+el9.6.0+90588+1a9ecb62
nodejs-docs
22.15.0-1.module+el9.6.0+90588+1a9ecb62
nodejs-full-i18n
22.15.0-1.module+el9.6.0+90588+1a9ecb62
nodejs-libs
22.15.0-1.module+el9.6.0+90588+1a9ecb62
nodejs-nodemon
3.0.1-1.module+el9.6.0+90588+1a9ecb62
nodejs-packaging
2021.06-4.module+el9.6.0+90588+1a9ecb62
nodejs-packaging-bundler
2021.06-4.module+el9.6.0+90588+1a9ecb62
npm
10.9.2-1.22.15.0.1.module+el9.6.0+90588+1a9ecb62
v8-12.4-devel
12.4.254.21-1.22.15.0.1.module+el9.6.0+90588+1a9ecb62
Связанные CVE
Связанные уязвимости
c-ares is an asynchronous resolver library. From 1.32.3 through 1.34.4, there is a use-after-free in read_answers() when process_answer() may re-enqueue a query either due to a DNS Cookie Failure or when the upstream server does not properly support EDNS, or possibly on TCP queries if the remote closed the connection immediately after a response. If there was an issue trying to put that new transaction on the wire, it would close the connection handle, but read_answers() was still expecting the connection handle to be available to possibly dequeue other responses. In theory a remote attacker might be able to trigger this by flooding the target with ICMP UNREACHABLE packets if they also control the upstream nameserver and can return a result with one of those conditions, this has been untested. Otherwise only a local attacker might be able to change system behavior to make send()/write() return a failure condition. This vulnerability is fixed in 1.34.5.
c-ares is an asynchronous resolver library. From 1.32.3 through 1.34.4, there is a use-after-free in read_answers() when process_answer() may re-enqueue a query either due to a DNS Cookie Failure or when the upstream server does not properly support EDNS, or possibly on TCP queries if the remote closed the connection immediately after a response. If there was an issue trying to put that new transaction on the wire, it would close the connection handle, but read_answers() was still expecting the connection handle to be available to possibly dequeue other responses. In theory a remote attacker might be able to trigger this by flooding the target with ICMP UNREACHABLE packets if they also control the upstream nameserver and can return a result with one of those conditions, this has been untested. Otherwise only a local attacker might be able to change system behavior to make send()/write() return a failure condition. This vulnerability is fixed in 1.34.5.
c-ares is an asynchronous resolver library. From 1.32.3 through 1.34.4, there is a use-after-free in read_answers() when process_answer() may re-enqueue a query either due to a DNS Cookie Failure or when the upstream server does not properly support EDNS, or possibly on TCP queries if the remote closed the connection immediately after a response. If there was an issue trying to put that new transaction on the wire, it would close the connection handle, but read_answers() was still expecting the connection handle to be available to possibly dequeue other responses. In theory a remote attacker might be able to trigger this by flooding the target with ICMP UNREACHABLE packets if they also control the upstream nameserver and can return a result with one of those conditions, this has been untested. Otherwise only a local attacker might be able to change system behavior to make send()/write() return a failure condition. This vulnerability is fixed in 1.34.5.
