CVE-2023-45286: HTTP request body disclosure in github.com/go-resty/resty/v2

Published Nov 28, 2023
·
Updated

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.

Affected Software

5 affected componentsFixes available
go/github.com/go-resty/resty/v2>=2.10.0<2.11.0
2.11.0
Resty Project Resty Go<=2.10.0
IBM Fusion<=2.2.0 - 2.10.1
IBM Fusion HCI<=2.2.0 - 2.10.0
IBM Fusion HCI for watsonx<=2.8.2 - 2.10.0

Event History

Nov 28, 2023
CVE Published
via MITRE·04:31 PM
Data Sourced
via MITRE·04:31 PM
DescriptionWeakness
Advisory Published
05:36 PM
Nov 29, 2023
Data Sourced
via Red Hat·01:55 AM
DescriptionSeverityAffected Software
Sep 11, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the vulnerability ID for this issue?

The vulnerability ID for this issue is CVE-2023-45286.

2

What is the title of this vulnerability?

The title of this vulnerability is 'HTTP request body disclosure in github.com/go-resty/resty/v2'.

3

How can this vulnerability be triggered?

This vulnerability 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.

4

What is the affected software?

The affected software is the 'github.com/go-resty/resty/v2' package with a version of 2.10.0 or higher.

5

Are there any references for this vulnerability?

Yes, you can find the references for this vulnerability at the following links: [Link 1](https://github.com/go-resty/resty/issues/743), [Link 2](https://github.com/go-resty/resty/issues/739), [Link 3](https://github.com/go-resty/resty/pull/745).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203