Information Exposure Through Log Files Affecting cloudbeat-fips-9.0 package, versions <9.0.8-r34


Severity

Recommended
0.0
medium
0
10

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

Threat Intelligence

EPSS
0.67% (49th 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-CHAINGUARDLATEST-CLOUDBEATFIPS90-17799252
  • published2 Jul 2026
  • disclosed12 Dec 2023

Introduced: 12 Dec 2023

CVE-2023-49922  (opens in a new tab)
CWE-532  (opens in a new tab)

How to fix?

Upgrade Chainguard cloudbeat-fips-9.0 to version 9.0.8-r34 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cloudbeat-fips-9.0 package and not the cloudbeat-fips-9.0 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

An issue was discovered by Elastic whereby Beats and Elastic Agent would log a raw event in its own logs at the WARN or ERROR level if ingesting that event to Elasticsearch failed with any 4xx HTTP status code except 409 or 429. Depending on the nature of the event that Beats or Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the Beats or Elastic Agent logs. Elastic has released 8.11.3 and 7.17.16 that prevents this issue by limiting these types of logs to DEBUG level logging, which is disabled by default.

CVSS Base Scores

version 3.1