https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 10 Oct 2026 22:43:19 +0000 https://vulnerability.circl.lu/vuln/ghsa-5c9x-8gcm-mpgx <p><strong>Affected:</strong> npm: axios</p> <p>### Summary</p> <p>For stream request bodies, maxBodyLength is bypassed when maxRedirects is set to 0 (native http/https transport path). Oversized streamed uploads are sent fully even when the caller sets strict body limits.</p> <p>### Details</p> <p>Relevant flow in lib/adapters/http.js: - 556-564: maxBodyLength check applies only to buffered/non-stream data. - 681-682: maxRedirects === 0 selects native http/https transport. - 694-699: options.maxBodyLength is set, but native transport does not enforce it. - 925-945: stream is piped directly to socket (data.pipe(req)) with no Axios byte counting.</p> <p>This creates a path-specific bypass for streamed uploads.</p> <p>### PoC</p> <p>Environment:</p> <p>- Axios main at commit f7a4ee2 - Node v24.2.0</p> <p>Steps: 1. Start an HTTP server that counts uploaded bytes and returns {received}. 2. Send a 2 MiB Readable stream with: - adapter: &#39;http&#39; - maxBodyLength: 1024 - maxRedirects: 0</p> <p>Observed: - Request succeeds; server reports received: 2097152.</p> <p>Control checks: - Same stream with default/nonzero redirects: rejected with ERR_FR_MAX_BODY_LENGTH_EXCEEDED. - Buffered body with maxRedirects: 0: rejected with ERR_BAD_REQUEST.</p> <p>### Impact Type: DoS / uncontrolled upstream upload / resource exhaustion. Impacted: Node.js services using streamed request bodies with maxBodyLength expecting hard enforcement, especially when following Axios guidance to use maxRedirects: 0 for streams.</p> <p><strong>Affected:</strong> npm: axios</p> <p>### Summary</p> <p>For stream request bodies, maxBodyLength is bypassed when maxRedirects is set to 0 (native http/https transport path). Oversized streamed uploads are sent fully even when the caller sets strict body limits.</p> <p>### Details</p> <p>Relevant flow in lib/adapters/http.js: - 556-564: maxBodyLength check applies only to buffered/non-stream data. - 681-682: maxRedirects === 0 selects native http/https transport. - 694-699: options.maxBodyLength is set, but native transport does not enforce it. - 925-945: stream is piped directly to socket (data.pipe(req)) with no Axios byte counting.</p> <p>This creates a path-specific bypass for streamed uploads.</p> <p>### PoC</p> <p>Environment:</p> <p>- Axios main at commit f7a4ee2 - Node v24.2.0</p> <p>Steps: 1. Start an HTTP server that counts uploaded bytes and returns {received}. 2. Send a 2 MiB Readable stream with: - adapter: &#39;http&#39; - maxBodyLength: 1024 - maxRedirects: 0</p> <p>Observed: - Request succeeds; server reports received: 2097152.</p> <p>Control checks: - Same stream with default/nonzero redirects: rejected with ERR_FR_MAX_BODY_LENGTH_EXCEEDED. - Buffered body with maxRedirects: 0: rejected with ERR_BAD_REQUEST.</p> <p>### Impact Type: DoS / uncontrolled upstream upload / resource exhaustion. Impacted: Node.js services using streamed request bodies with maxBodyLength expecting hard enforcement, especially when following Axios guidance to use maxRedirects: 0 for streams.</p> https://vulnerability.circl.lu/vuln/ghsa-5c9x-8gcm-mpgx