Node.js fixes 16 flaws, two in HTTP/2: update now
Node.js security releases fix 16 flaws, including an HTTP/2 crash and a data leak between connections. Here is who is affected and how to check.
TL;DR: The Node.js project fixed 16 flaws this week, including two in its built-in HTTP/2 support: one lets unauthenticated clients crash a server, and one can leak data meant for other connections. Move to the patched build for your release line: 26.13.1, 24.22.3 or 22.23.5.
What happened
The Hacker News reported that Node.js shipped security releases for all three supported lines. The crash flaw hits servers where Node.js itself speaks HTTP/2, on the 24.x and 26.x lines, and an attacker needs no login. A second HTTP/2 flaw can hand a client fragments of server memory, which may include responses meant for other connections.
The patched builds are 26.13.1, 24.22.3 and 22.23.5. The report does not say that either HTTP/2 flaw is exploited, so treat this as a patch to schedule soon rather than an emergency. Still, a crash that any visitor can trigger is a cheap way to take a service down, and a memory leak across connections can expose session data. Read the Node.js release notes for the full list of the other fixes.
Am I affected?
You are affected if you run Node.js on one of those three lines and your application serves HTTP/2 directly from Node.js. If a reverse proxy or load balancer terminates HTTP/2 and forwards plain requests to Node.js, the exposure is different, but you should still update, because the release also carries the other fixes. To see the version on one machine, run:
node --versionAlso check the Node.js version named in each Dockerfile and in your CI images, since images often lag behind the hosts.
How to check with Stackurity
Stackurity keeps one live inventory of servers, deployed applications, repositories and container images, and matches it against new advisories every hour. A read-only agent finds Node.js on Linux servers, repositories and images can be added, and the opt-in Docker setting reads the images of running containers. Matching uses each ecosystem's own version rules, and after you upgrade, check again records whether the issue is really gone. Node.js copied into an application outside a package manager, or statically linked, is not covered. See how Stackurity handles fixes. Stackurity Cloud has a 30-day trial: start a free trial.