# CVE-2023-49922: GO-2023-2413 - Sensitive information logged in github.com/elastic/beats/v7

Source: https://junglewise.ai/threats/cve-2023-49922-elastic-beats-inserts-sensitive-information-into-log-file  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2024-01-03  
License: CC BY 4.0 with a link back

CVE-2023-49922 · Severity: low · CVSS 3.1 · Published 2024-01-03

Sensitive information logged in github.com/elastic/beats/v7

Technologies: [github.com/elastic/beats (Go)](https://junglewise.ai/threats/technologies/github-com-elastic-beats), [github.com/elastic/beats/v7 (Go)](https://junglewise.ai/threats/technologies/github-com-elastic-beats-v7). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2023-49922 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2023-49922 being exploited in the wild.

**How severe is CVE-2023-49922?** Low severity, with a CVSS score of 3.1, published 3 January 2024.

**Which products and versions are affected?** github.com/elastic/beats (Go) SEMVER:introduced=8.0.0,fixed=8.11.3; github.com/elastic/beats/v7 (Go) SEMVER:introduced=0,fixed=7.17.16, SEMVER:introduced=7.0.0,fixed=7.17.16.

**Is there a fix for CVE-2023-49922?** Yes. github.com/elastic/beats (Go): upgrade to 8.11.3 or later; github.com/elastic/beats/v7 (Go): upgrade to 7.17.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2023-49922?** Check whether you run github.com/elastic/beats (Go) or github.com/elastic/beats/v7 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/elastic/beats (Go): upgrade to 8.11.3 or later

  ```sh
  go get github.com/elastic/beats@v8.11.3
  ```

- github.com/elastic/beats/v7 (Go): upgrade to 7.17.16 or later

  ```sh
  go get github.com/elastic/beats/v7@v7.17.16
  ```


## Affected products

- github.com/elastic/beats (Go) SEMVER:introduced=8.0.0,fixed=8.11.3
- github.com/elastic/beats/v7 (Go) SEMVER:introduced=0,fixed=7.17.16, SEMVER:introduced=7.0.0,fixed=7.17.16

## Identifiers

- CVE-2023-49922
- GHSA-hj4r-2c9c-29h3
- GO-2023-2413

## Related threats

- [Packetbeat does not properly validate an array index in multiple protocol parser components](https://junglewise.ai/threats/cve-2026-26933-packetbeat-does-not-properly-validate-an-array-index-in-multiple)
- [Elastic Metricbeat Prometheus remote_write denial of service](https://junglewise.ai/threats/cve-2026-26931-elastic-metricbeat-prometheus-remote-write-denial-of-service)
- [GO-2026-4360 - Metricbeat affected by multiple denial of service vulnerabilities in github.com/elastic/beats](https://junglewise.ai/threats/cve-2026-0528-metricbeat-affected-by-multiple-denial-of-service-vulnerabilities)
- [GO-2025-4252 - Buffer Overflow via Malformed Syslog Message or Malicious Tokenizer Pattern in github.com/elastic/beats](https://junglewise.ai/threats/cve-2025-68383-filebeat-beats-has-buffer-overflow-via-malformed-syslog-message)
- [Elasticsearch Packetbeat has Excessive Allocation of Memory and CPU via Malicious IPv4 Fragments](https://junglewise.ai/threats/cve-2025-68388-elasticsearch-packetbeat-has-excessive-allocation-of-memory-and)