Executive Summary

This vulnerability occurs when a malformed HTTP/2 HEADERS frame containing oversized or invalid HPACK data causes Node.js to crash. The crash happens because an unhandled TLSSocket error (ECONNRESET) is triggered, and instead of safely closing the connection, the Node.js process terminates unexpectedly. This mainly affects applications that do not have explicit error handlers attached to secure sockets.

Useful 0 Not Useful 0

Impact Analysis

The vulnerability can lead to a remote denial of service (DoS) attack by causing the Node.js process to crash unexpectedly. This can disrupt the availability of applications or services running on Node.js that are exposed to malicious HTTP/2 traffic without proper error handling on secure sockets.

Useful 0 Not Useful 0

Mitigation Strategies

To mitigate this vulnerability, ensure that your Node.js applications attach explicit error handlers to secure sockets to prevent the process from crashing due to unhandled TLSSocket errors. For example, add an error event listener on the secureConnection event as follows: server.on('secureConnection', socket => { socket.on('error', err => { console.log(err); }); });

Useful 0 Not Useful 0