boringproxy 0.10.0 Resource Exhaustion DoS via GET /loading endpoint
38Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 7.1
exploitation probability
—
observed exploitation
nono source reports it
1 public exploit(s)
boringproxy through 0.10.0 contains a resource exhaustion vulnerability that allows any authenticated user to permanently exhaust server file descriptors, goroutines, and memory by sending requests to the GET /loading endpoint with attacker-supplied id query parameter values. Because the handler performs no map-lookup validity check and receives on a nil channel that blocks forever, with no timeout, no context cancellation, and no server-side reclamation due to absent HTTP server timeouts, each malicious request permanently holds one goroutine, one file descriptor, and approximately 50 kB of memory until the server's file descriptor limit is reached and listener Accept calls fail, halting all tunnel traffic forwarding for all users.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Affected products
boringproxy · boringproxypublic PoCs found — 1
cve_referencegithub.com/theopaid/Denial-Of-Service-Through-Unbounded-Resource-Consumption-In-Request-Handler-boringproxy-/blob/master/README.mdunverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.