nodejs

Go to file

openeuler-ci-bot a3a6fe9720

!188 correct error related to CVE-2025-23085

From: @aaronhans 
Reviewed-by: @wang--ge 
Signed-off-by: @wang--ge

2025-04-11 06:42:24 +00:00

0001-Disable-running-gyp-on-shared-deps.patch

Update to 12.18.4

2020-11-19 15:22:19 +08:00

0002-Install-both-binaries-and-use-libdir.patch

Update to 12.18.4

2020-11-19 15:22:19 +08:00

0004-Make-AARCH64-compile-on-64KB-physical-pages.patch

Make AARCH64 compile on 64KB physical pages to fix build error

2021-01-04 10:29:03 +08:00

0005-use-getauxval-in-node_main_cc.patch

use getauxval to fix build failure in node_main.cc

2021-08-16 13:40:04 +08:00

0006-add-loong64-support-12.22.11.patch

Fix CVE-2023-0464 and CVE-2023-0465

2024-02-05 18:00:52 +08:00

0007-correct-some-errors-related-to-CVE-2025-23085.patch

1.According to the description above error line in node_http2.cc,this should be checking whether frame->hd.type is NGHTTP2_GOAWAY,and the value of NGHTTP2_GOAWAY is 0x07,however,it is written as 0x03 here,which i think it is an error;2.correct the error of http2 header frame content based on http2 related protocal so that make UT script exited successfully

2025-04-11 09:40:05 +08:00

btest402.js

Update to 10.21.0

2020-08-25 14:24:57 +08:00

CVE-2022-4304.patch

Fix CVE-2023-0286,CVE-2023-0215,CVE-2022-4304 and CVE-2022-4450

2023-02-23 10:00:45 +08:00

CVE-2022-4450.patch

Fix CVE-2023-0286,CVE-2023-0215,CVE-2022-4304 and CVE-2022-4450

2023-02-23 10:00:45 +08:00

CVE-2022-25881.patch

Fix CVE-2022-32212,CVE-2022-32213,CVE-2022-32214,CVE-2022-32215,CVE-2022-25881,CVE-2023-23918,CVE-2023-23920,CVE-2023-30589,CVE-2023-30590,CVE-2023-30581,CVE-2023-32002,CVE-2023-32006,CVE-2023-32559,CVE-2022-35256

2023-08-29 17:18:30 +08:00

CVE-2022-32212.patch

2023-08-29 17:18:30 +08:00

CVE-2022-32213-CVE-2022-32214-CVE-2022-32215.patch

2023-08-29 17:18:30 +08:00

CVE-2022-35256.patch

2023-08-29 17:18:30 +08:00

CVE-2022-43548.patch

2023-08-29 17:18:30 +08:00

CVE-2023-0215.patch

Fix CVE-2023-0286,CVE-2023-0215,CVE-2022-4304 and CVE-2022-4450

2023-02-23 10:00:45 +08:00

CVE-2023-0286.patch

Fix CVE-2023-0286,CVE-2023-0215,CVE-2022-4304 and CVE-2022-4450

2023-02-23 10:00:45 +08:00

CVE-2023-0464.patch

Fix CVE-2023-0464 and CVE-2023-0465

2024-02-05 18:00:52 +08:00

CVE-2023-0465.patch

Fix CVE-2023-0464 and CVE-2023-0465

2024-02-05 18:00:52 +08:00

CVE-2023-23918.patch

Update CVE-2023-23918.patch for fix nodejs-raw-body,nodejs-istanbul build error

2023-10-26 14:51:55 +08:00

CVE-2023-23920.patch

2023-08-29 17:18:30 +08:00

CVE-2023-30581.patch

2023-08-29 17:18:30 +08:00

CVE-2023-30589.patch

2023-08-29 17:18:30 +08:00

CVE-2023-30590.patch

2023-08-29 17:18:30 +08:00

CVE-2023-32002-CVE-2023-32006.patch

2023-08-29 17:18:30 +08:00

CVE-2023-32559.patch

2023-08-29 17:18:30 +08:00

CVE-2023-44487.patch

Fix CVE-2023-44487

2024-02-06 18:08:01 +08:00

CVE-2023-46809.patch

Fix CVE-2023-46809,CVE-2024-22019,CVE-2024-22025,CVE-2024-27982 and CVE-2024-27983

2024-09-19 16:23:44 +08:00

CVE-2024-22019.patch

Fix CVE-2023-46809,CVE-2024-22019,CVE-2024-22025,CVE-2024-27982 and CVE-2024-27983

2024-09-19 16:23:44 +08:00

CVE-2024-22025.patch

Fix CVE-2023-46809,CVE-2024-22019,CVE-2024-22025,CVE-2024-27982 and CVE-2024-27983

2024-09-19 16:23:44 +08:00

CVE-2024-27982.patch

Fix CVE-2023-46809,CVE-2024-22019,CVE-2024-22025,CVE-2024-27982 and CVE-2024-27983

2024-09-19 16:23:44 +08:00

CVE-2024-27983.patch

Fix CVE-2023-46809,CVE-2024-22019,CVE-2024-22025,CVE-2024-27982 and CVE-2024-27983

2024-09-19 16:23:44 +08:00

CVE-2025-23085.patch

Fix CVE-2025-23085

2025-03-06 10:10:47 +08:00

icu4c-67_1-src.tgz

Update to 12.18.4

2020-11-19 15:22:19 +08:00

node-v12.22.11.tar.gz

Update to 12.22.11, fix some cves.

2022-03-28 16:06:17 +08:00

nodejs_native.attr

package init

2020-03-06 18:04:34 +08:00

nodejs.spec

2025-04-11 09:40:05 +08:00

nodejs.yaml

Update to 12.18.4

2020-11-19 15:22:19 +08:00

npmrc

Update to 12.18.4

2020-11-19 15:22:19 +08:00