Proposal: build official Node.js binaries for glibc-based Linux using PIE, enables ASLR, helps prevent RCE
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript, linux, node.js
- 领域
- build-system, security
调研方向
Read the linked discussion in issue #33425 and compare the current Linux binary build configuration for glibc x64 with the musl and ARM builds. Assess the performance and security tradeoffs of enabling PIE for official glibc x64 binaries; done means the project has decided whether to change the build and documented the resulting scope.
由索引模型根据 Issue 内容生成。
描述
What is the problem this feature will solve?
Almost all operating systems enable Address Space Layout Randomisation (ASLR) to help prevent memory-related vulnerabilities from reaching a state where Remote Code Execution (RCE) is possible.
To take full advantage of this protection, an executable must be compiled as a Position Independent Executable (PIE).
The current state of PIE in Node.js is as follows:
-
✅ macOS - PIE since 2020 via https://github.com/nodejs/node/pull/35704
-
⏳ Windows - PIE via
/DYNAMICBASEbeing proposed at https://github.com/nodejs/node/issues/64212 -
✅ Linux using musl libc - PIE is compiler default for all executables
-
✅ Linux using glibc where
nodebinary is compiled and provided by OS package manager - PIE is default for almost all OS-level package repositories -
❌ Linux using glibc where
nodebinary is provided by Node.js - Not PIE
What is the feature you are proposing to solve the problem?
A previous discussion from May 2020 rejected use of PIE on Linux due to a expected performance penalty of 5-10% and, at that point in time, little evidence of RCE within the Node.js ecosystem.
Given many organisations already quite happily use Node.js with PIE/ASLR, be that on macOS, via Alpine Linux based containers or OS-provided packages, is it time to revisit this discussion for those left behind?
The performance impact of PIE is negligible on 64-bit ARM CPUs, which have seen increasing adoption since 2020 e.g. AWS Graviton.
Do the security benefits of PIE now outweigh the performance cost for those still running glibc-based Linux on x64 architecture CPUs?
By way of a recent example, had this change already been in place then it's likely CVE-2026-111497 would have been rated "High" rather than "Critical" severity.
What alternatives have you considered?
If there's still a desire to provide official binaries for a subset of platforms without PIE then perhaps offering a security-hardened alternative with PIE might help raise awareness.
- 主要语言
- JavaScript
- 星标
- 123k
- 派生
- 39.9k
- 平均合并
- 4 天 11 小时
- 30 天内合并 PR
- 228
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nodejs/node 的其他 Issue
-
url: pathToFileURL duplicates root slash across platforms and misses empty extended UNC servername可能已有人在做 @JoaoMarcos44 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
Docs: --watch-path *is* supported on linux可能已有人在做 @motokaneyuki 于 14 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 82/100
nodejs/node#66743 · 1 个 reaction ·
维护者通常 1 天内回复
-
node:internal/inspector/network_http: `TypeError: Missing dataLength` in event when response uses `setEncoding()`可能已有人在做 @lazerg 于 23 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
[Docs] `process.loadEnvFile()` does not document behaviour when variables already exist可能已有人在做 @Sepandard 于 32 天前认领。 未关闭doc
难度 1/5 1 小时以内 新手友好度 90/100
维护者通常 1 天内回复
-
Stream.prototype.forEach will block in first promise in queue before read more chunk可能已有人在做 @mmustafasenoglu 于 33 天前认领。 未关闭doc
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
相似的 Issue
-
admission-deferred priority: medium status: ready work-class: scoped
难度 2/5 1-3 小时 新手友好度 70/100
melodic-software/claude-code-plugins#10887 · 4 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
-
难度 1/5 1-3 小时 新手友好度 91/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 2 天内回复
-
enhancement ui-dashboard
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复