3 people 51f4de4b4a src,lib: refactor unsafe buffer creation to remove zero-fill toggle ...

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

2026-01-09 11:44:02 -03:00

..

async_resource.cc

src: add a constructor overload for CallbackScope

2021-08-21 06:53:50 +00:00

callback.cc

src: refactor GetCreationContext calls

2024-03-25 19:22:37 +00:00

embed_helpers.cc

src: add string_view overload to snapshot FromBlob

2024-05-03 08:30:34 +02:00

encoding.cc

crypto: implement crypto.hash()

2024-03-25 19:27:53 +00:00

environment.cc

src,lib: refactor unsafe buffer creation to remove zero-fill toggle

2026-01-09 11:44:02 -03:00

exceptions.cc

src: fix winapi_strerror error string

2025-01-24 22:17:32 +01:00

hooks.cc

src: simplify exit code accesses

2022-11-10 01:09:18 +00:00

utils.cc

src: cleanup unused headers

2019-11-28 23:21:08 +01:00