概要
認証なしで、他の接続の通信内容や TLS の秘密鍵をメモリから読まれるおそれ。
元の説明(英語)を読む
A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScript running inside the HTTP parser's on_body callback, ClearOut() decrypts the next TLS record while the parser is still mid-body, re-entering llhttp_execute() and causing a use-after-free and an out-of-bounds heap read. The server then copies that freed or unrelated heap memory into the response for the request body. Triggering it requires a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, and reading the leaked memory requires any ordinary route that echoes or stores a request body. Cleartext node:http is not affected. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
影響を受ける人
HTTPS を使う Node.js 22・24・26 の管理者
対策
- Node.js を 22.23.5・24.22.3・26.13.1 のいずれか以降に更新する
国内の動き
本文に同じ CVE 番号のある国内の注意喚起・報道は、まだ無い。
海外の動き
- The Hacker News(報道)↗11/12
PoC
公開されている PoC は、まだ見つかっていない。