Request Filtering Agent
Monthly
Denial of service in the request-filtering-agent npm package (all versions prior to 3.2.1) lets remote attackers terminate a Node.js process by causing the application to request a literal private or reserved IP address such as 127.0.0.1 or the cloud-metadata address 169.254.169.254. RequestFilteringHttpAgent and RequestFilteringHttpsAgent threw synchronously from createConnection when rejecting such a literal IP; because Node's http.request/http.get expect connection failures to arrive asynchronously, the throw escaped req.on('error') and surfaced as an uncaught exception that crashes the process (CWE-248). The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5), so exploitation is unauthenticated but strictly an availability impact - the private-IP filter itself still rejects the request, and no confidentiality or integrity loss is assessed. No public exploit code has been identified at time of analysis, and there is no CISA KEV listing; successful exploitation additionally requires the consuming application to let attacker input reach the agent as a bare IP literal rather than a hostname.
Denial of service in the request-filtering-agent npm package (all versions prior to 3.2.1) lets remote attackers terminate a Node.js process by causing the application to request a literal private or reserved IP address such as 127.0.0.1 or the cloud-metadata address 169.254.169.254. RequestFilteringHttpAgent and RequestFilteringHttpsAgent threw synchronously from createConnection when rejecting such a literal IP; because Node's http.request/http.get expect connection failures to arrive asynchronously, the throw escaped req.on('error') and surfaced as an uncaught exception that crashes the process (CWE-248). The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5), so exploitation is unauthenticated but strictly an availability impact - the private-IP filter itself still rejects the request, and no confidentiality or integrity loss is assessed. No public exploit code has been identified at time of analysis, and there is no CISA KEV listing; successful exploitation additionally requires the consuming application to let attacker input reach the agent as a bare IP literal rather than a hostname.