CVE-2023-45286
A race condition in go-resty can result in HTTP request body disclosure across requests.
Does this matter?
Lower severity and a low EPSS score (0.73%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 5.9 MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 0.73% probability · 52th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-362
- Affected
- resty project/resty
- Source
- security@golang.org
References
- https://github.com/go-resty/resty/commit/577fed8730d79f583eb48dfc81674164e1fc471e
- https://github.com/go-resty/resty/issues/739Exploit, Issue Tracking
- https://github.com/go-resty/resty/issues/743Issue Tracking
- https://github.com/go-resty/resty/pull/745Issue Tracking, Patch
- https://pkg.go.dev/vuln/GO-2023-2328Vendor Advisory
- https://github.com/go-resty/resty/commit/577fed8730d79f583eb48dfc81674164e1fc471e
- https://github.com/go-resty/resty/issues/739Exploit, Issue Tracking
- https://github.com/go-resty/resty/issues/743Issue Tracking
- https://github.com/go-resty/resty/pull/745Issue Tracking, Patch
- https://pkg.go.dev/vuln/GO-2023-2328Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.