Race Condition Affecting golang-github-go-resty-resty package, versions <2.10.0-2


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.73% (50th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN13-GOLANGGITHUBGORESTYRESTY-6095006
  • published30 Nov 2023
  • disclosed28 Nov 2023

Introduced: 28 Nov 2023

CVE-2023-45286  (opens in a new tab)
CWE-362  (opens in a new tab)

How to fix?

Upgrade Debian:13 golang-github-go-resty-resty to version 2.10.0-2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream golang-github-go-resty-resty package and not the golang-github-go-resty-resty package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

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 Base Scores

version 3.1