boringproxy 0.10.0 Resource Exhaustion DoS via GET /loading endpoint
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| boringproxy | boringproxy | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Boringproxy | Boringproxy |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.336% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Boringproxy
Boringproxy boringproxy |
|
| Vendors & Products |
Boringproxy
Boringproxy boringproxy |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | boringproxy 0.10.0 Resource Exhaustion DoS via GET /loading endpoint | |
| Weaknesses | CWE-833 | |
| References |
| |
| Metrics |
cvssV3_1
|