github.com/go-resty/resty/v2 HTTP request body disclosure
A race condition in go-resty can result in HTTP request body disclosure across requests. This condition can be triggered by calling sync.Pool.Put with the same *bytes.Buffer more than once, when request retries are enabled and a retry occurs. The call to sync.Pool.Get will then return a bytes.Buffer that hasn't had bytes.Buffer.Reset called on it. This dirty buffer will contain the HTTP request body from an unrelated request, and go-resty will append the current HTTP request body to it, sending two bodies in one request. The sync.Pool in question is defined at package level scope, so a completely unrelated server could receive the request body.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-45286US | medium5.9 | — | ||
A race condition in go-resty can result in HTTP request body disclosure across requests. This condition can be triggered by calling sync.Pool.Put with the same *bytes.Buffer more t… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/go-resty/restyPACKAGE
- https://github.com/go-resty/resty/commit/577fed8730d79f583eb48dfc81674164e1fc471eWEB
- https://github.com/go-resty/resty/issues/739WEB
- https://github.com/go-resty/resty/issues/743WEB
- https://github.com/go-resty/resty/pull/745WEB
- https://github.com/go-resty/resty/releases/tag/v2.11.0WEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-45286ADVISORY
- https://pkg.go.dev/vuln/GO-2023-2328WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan