This removes the zero-fill toggle mechanism that allowed JavaScript to control ArrayBuffer initialization via shared memory. Instead, unsafe buffer creation now uses a dedicated C++ API. Refs: https://hackerone.com/reports/3405778 Co-Authored-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Co-Authored-By: Joyee Cheung <joyeec9h3@gmail.com> Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com> PR-URL: https://github.com/nodejs-private/node-private/pull/759 Backport-PR-URL: https://github.com/nodejs-private/node-private/pull/799 CVE-ID: CVE-2025-55131 |
||
|---|---|---|
| .. | ||
| execution.js | ||
| per_thread.js | ||
| permission.js | ||
| policy.js | ||
| pre_execution.js | ||
| promises.js | ||
| report.js | ||
| signal.js | ||
| task_queues.js | ||
| warning.js | ||
| worker_thread_only.js | ||