Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

HTTP request body disclosure in github.com/go-resty/resty/v2

cve-program · severity unknowneuvd · severity unknownCVSS 3.1 · [email protected] · Primary 5.9 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/go-resty/resty/v2 2.11.0osv · severity unknownFixed by github.com/go-resty/resty/v2 2.11.0KEV status unknown

cve-program · CVE-2023-45286

Published

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.

Read the publisher's advisory

euvd · EUVD-2023-3068

Published

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.

Read the publisher's advisory

nvd · CVE-2023-45286

Published

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.

Read the publisher's advisory

osv · GHSA-xwh9-gc39-5298

Published

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.

Read the publisher's advisory

osv · GO-2023-2328

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2023-45286

Published

HTTP request body disclosure in github.com/go-resty/resty/v2

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.

Source published
28 Nov 2023 16:31:21 UTC
Source modified
28 Aug 2024 20:01:23 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

euvd · EUVD-2023-3068

Published

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 occur…

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Nov 28, 2023, 4:31:21 PM

dateUpdated: Aug 28, 2024, 8:01:23 PM

5 related source bulletins · separate from aliases

WID-SEC-W-2024-1226: Red Hat OpenShift: Mehrere Schwachstellen

CVE-2020-26555 · CVE-2021-25220 · CVE-2021-29390 · CVE-2021-43618 · CVE-2022-0480 · CVE-2022-2795 · CVE-2022-3094 · CVE-2022-38096 · CVE-2022-40090 · CVE-2022-45934 · CVE-2022-48554 · CVE-2022-48624 · CVE-2023-24023 · CVE-2023-25193 · CVE-2023-25775 · CVE-2023-26159 · CVE-2023-26364 · CVE-2023-28322 · CVE-2023-28464 · CVE-2023-28866 · CVE-2023-2975 · CVE-2023-31083 · CVE-2023-31122 · CVE-2023-3446 · CVE-2023-3567 · CVE-2023-3618 · CVE-2023-37453 · CVE-2023-3817 · CVE-2023-38469 · CVE-2023-38470 · CVE-2023-38471 · CVE-2023-38472 · CVE-2023-38473 · CVE-2023-38546 · CVE-2023-39189 · CVE-2023-39193 · CVE-2023-39194 · CVE-2023-39198 · CVE-2023-39326 · CVE-2023-40745 · CVE-2023-41175 · CVE-2023-4133 · CVE-2023-42754 · CVE-2023-42756 · CVE-2023-43785 · CVE-2023-43786 · CVE-2023-43787 · CVE-2023-43788 · CVE-2023-43789 · CVE-2023-4408 · CVE-2023-45286 · CVE-2023-45287 · CVE-2023-45288 · CVE-2023-45289 · CVE-2023-45290 · CVE-2023-45857 · CVE-2023-45863 · CVE-2023-46218 · CVE-2023-46862 · CVE-2023-47038 · CVE-2023-48631 · CVE-2023-50387 · CVE-2023-50868 · CVE-2023-51043 · CVE-2023-51779 · CVE-2023-51780 · CVE-2023-52425 · CVE-2023-52434 · CVE-2023-52448 · CVE-2023-52476 · CVE-2023-52489 · CVE-2023-52522 · CVE-2023-52529 · CVE-2023-52574 · CVE-2023-52578 · CVE-2023-52580 · CVE-2023-52581 · CVE-2023-52597 · CVE-2023-52610 · CVE-2023-52620 · CVE-2023-5678 · CVE-2023-6040 · CVE-2023-6121 · CVE-2023-6129 · CVE-2023-6176 · CVE-2023-6228 · CVE-2023-6237 · CVE-2023-6240 · CVE-2023-6531 · CVE-2023-6546 · CVE-2023-6622 · CVE-2023-6915 · CVE-2023-6931 · CVE-2023-6932 · CVE-2023-7008 · CVE-2024-0565 · CVE-2024-0727 · CVE-2024-0841 · CVE-2024-1085 · CVE-2024-1086 · CVE-2024-1394 · CVE-2024-1488 · CVE-2024-21011 · CVE-2024-21012 · CVE-2024-21068 · CVE-2024-21085 · CVE-2024-21094 · CVE-2024-22365 · CVE-2024-24783 · CVE-2024-24784 · CVE-2024-24785 · CVE-2024-24786 · CVE-2024-25062 · CVE-2024-25742 · CVE-2024-25743 · CVE-2024-26582 · CVE-2024-26583 · CVE-2024-26584 · CVE-2024-26585 · CVE-2024-26586 · CVE-2024-26593 · CVE-2024-26602 · CVE-2024-26609 · CVE-2024-26633 · CVE-2024-27316 · CVE-2024-28834 · CVE-2024-28835 · CVE-2024-28849 · CVE-2024-29180 · CVE-2024-2961 · CVE-2024-33599 · CVE-2024-33600 · CVE-2024-33601 · CVE-2024-33602

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

CVE-2023-45286

openSUSE-SU-2024:13569-1: rclone-1.65.1-1.1 on GA media

CVE-2023-45286 · CVE-2023-48795

RHSA-2024:3621: Red Hat Security Advisory: Red Hat OpenShift distributed tracing 3.2.0 operator/operand containers update

CVE-2023-45286 · CVE-2023-45288 · CVE-2023-45289 · CVE-2023-45290 · CVE-2024-24783 · CVE-2024-24784 · CVE-2024-24785 · CVE-2024-24786

RHSA-2024:3316: Red Hat Security Advisory: Migration Toolkit for Applications security and bug fix update

CVE-2023-26159 · CVE-2023-26364 · CVE-2023-39326 · CVE-2023-45286 · CVE-2023-45287 · CVE-2023-45288 · CVE-2023-45857 · CVE-2023-48631 · CVE-2024-24786 · CVE-2024-28849 · CVE-2024-29180

Source published
Nov 28, 2023, 4:31:21 PM (timezone not stated)
Source modified
Aug 28, 2024, 8:01:23 PM (timezone not stated)
Saved here
19 Nov 2026 02:38:05 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

nvd · CVE-2023-45286

Published

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 occur…

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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-362

Original publisher date fields

published: 2023-11-28T17:15:08.280

lastModified: 2026-06-17T06:28:35.330

1 source CPE criteria · context only
  • cpe:2.3:a:resty_project:resty:*:*:*:*:*:go:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
28 Nov 2023 17:15:08 UTC
Source modified
17 Jun 2026 06:28:35 UTC
Saved here
24 Oct 2026 22:17:27 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Primary · 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

osv · GHSA-xwh9-gc39-5298

Published

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.

Source published
28 Nov 2023 17:36:21 UTC
Source modified
10 Sep 2026 03:49:59 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Publisher rating · MODERATE

osv · GO-2023-2328

Published

HTTP request body disclosure in github.com/go-resty/resty/v2

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.

Source published
27 Nov 2023 18:53:31 UTC
Source modified
4 Feb 2026 04:31:53 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 03:46 UTC · 273 of 275 readable · 270 fully read · documentation 469/469 current