Race Condition Affecting prometheus-fips package, versions <2.49.1-r1


Severity

Recommended
0.0
medium
0
10

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

Threat Intelligence

EPSS
0.16% (54th 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 Learn

Learn about Race Condition vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-PROMETHEUSFIPS-6186658
  • published24 Jan 2024
  • 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 Chainguard prometheus-fips to version 2.49.1-r1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream prometheus-fips package and not the prometheus-fips package as distributed by Chainguard. See How to fix? for Chainguard 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 Scores

version 3.1