Files
node/lib/internal
RafaelGSS 1b693fa03a src: fix HTTP2 mem leak on premature close and ERR_PROTO
This commit fixes a memory leak when the socket is
suddenly closed by the peer (without GOAWAY notification)
and when invalid header (by nghttp2) is identified and the
connection is terminated by peer.

Refs: https://hackerone.com/reports/2841362
PR-URL: https://github.com/nodejs-private/node-private/pull/650
Reviewed-By: James M Snell <jasnell@gmail.com>
CVE-ID: CVE-2025-23085
2025-01-21 15:53:42 -03:00
..
2024-09-24 19:48:15 +00:00
2024-09-25 14:35:18 +00:00
2025-01-03 09:49:21 +00:00
2024-10-09 06:42:16 +00:00
2024-09-09 17:24:10 +02:00
2024-04-25 19:14:16 +00:00
2024-10-09 06:42:16 +00:00
2024-10-09 06:42:16 +00:00
2024-09-24 19:48:15 +00:00
…
2024-12-04 09:29:30 -08:00
2024-09-24 22:26:59 +02:00
2024-08-27 14:58:36 +00:00
2024-02-19 01:19:44 +00:00
2025-01-14 18:24:30 +00:00

Internal Modules

The modules located in lib/internal directory are exclusively meant for internal usage within the Node.js core. They are not intended to be accessed via user modules require(). These modules may change at any point in time. Relying on these internal modules outside the core is not supported and can lead to unpredictable behavior.

In certain scenarios, accessing these internal modules for debugging or experimental purposes might be necessary. Node.js provides the --expose-internals flag to expose these modules to userland code. This flag only exists to assist Node.js maintainers with debugging internals. It is not meant for use outside the project.