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.
References
Link | Resource |
---|---|
https://github.com/go-resty/resty/commit/577fed8730d79f583eb48dfc81674164e1fc471e | |
https://github.com/go-resty/resty/issues/739 | Exploit Issue Tracking |
https://github.com/go-resty/resty/issues/743 | Issue Tracking |
https://github.com/go-resty/resty/pull/745 | Issue Tracking Patch |
https://pkg.go.dev/vuln/GO-2023-2328 | Vendor Advisory |
Configurations
History
No history.
Information
Published : 2023-11-28 17:15
Updated : 2024-01-04 19:15
NVD link : CVE-2023-45286
Mitre link : CVE-2023-45286
CVE.ORG link : CVE-2023-45286
JSON object : View
Products Affected
resty_project
- resty
CWE
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')