| 标题 | Node.js enquirer 2.4.1 Prototype Pollution |
|---|
| 描述 | Prototype pollution in the public `Enquirer` prompt flow when `question.name` contains dangerous path segments such as `__proto__`.
When a prompt is submitted, `Enquirer` stores the answer using an internal nested setter where the path is derived from the externally supplied `question.name`. Because dangerous segments like `__proto__`, `constructor`, and `prototype` are not rejected, a prompt name such as `__proto__.pp` can pollute `Object.prototype`.
This is reachable through the public package API via `new Enquirer()`, `register(...)`, and `prompt(...)`.
Impact: if an application allows attacker-controlled prompt definitions or otherwise passes untrusted values into `question.name`, an attacker may be able to trigger application-wide prototype pollution, leading to logic corruption, unsafe property resolution, denial of service, or downstream exploitation depending on how polluted properties are used. |
|---|
| 来源 | ⚠️ https://github.com/enquirer/enquirer/issues/487 |
|---|
| 用户 | Dremig (UID 95003) |
|---|
| 提交 | 2026-06-08 07時57分 (4 月前) |
|---|
| 管理 | 2026-07-09 07時15分 (1 month later) |
|---|
| 状态 | 已接受 |
|---|
| VulDB条目 | 377113 [enquirer 直到 2.4.1 Public Package API Enquirer.set question.name] |
|---|
| 积分 | 20 |
|---|