# CVE-2023-46672: Logstash Insertion of Sensitive Information into Log File

> Attackers with log access can read sensitive keystore data if Logstash uses non-default JSON logging.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Nov 2023
- **Updated:** 13 Feb 2025
- **Also known as:** BIT-logstash-2023-46672, GHSA-r6fg-prgw-3ff5

## What is CVE-2023-46672?

CVE-2023-46672 is a high-severity vulnerability in Elastic Logstash, published on 15 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was identified by Elastic whereby sensitive information is recorded in Logstash logs under specific circumstances.

The prerequisites for the manifestation of this issue are:

  *  Logstash  is configured to log in JSON format https://www.elastic.co/guide/en/logstash/current/running-logstash-command-line.html , which is not the default logging format.

  *  Sensitive data is stored in the Logstash keystore and referenced as a variable in Logstash configuration.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2023-46672?

1 open source package ship an affected version, including logstash. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `logstash` | Bitnami | From 7.12.1 | 7.12.2, 8.11.1 |

Products: Elastic Logstash.

## How do I fix CVE-2023-46672?

Upgrade logstash to a fixed version for your release line: 7.12.2 or 8.11.1.

## Is CVE-2023-46672 being exploited?

There is no known exploitation of CVE-2023-46672 in the wild and no public exploit code.

## Other vulnerabilities in Elastic Logstash

- [CVE-2019-7612](https://insights.sbomify.com/CVE-2019-7612/): Information disclosure in Logstash (critical 9.8)
- [CVE-2026-33466](https://insights.sbomify.com/CVE-2026-33466/): Improper Limitation of a Pathname to a Restricted Directory in Logstash Leading to Arbitrary File Write (high 8.1)
- [CVE-2019-7620](https://insights.sbomify.com/CVE-2019-7620/): Denial of service in Logstash (high 7.5)
- [CVE-2015-5378](https://insights.sbomify.com/CVE-2015-5378/): Information disclosure in n/a (high 7.5)
- [CVE-2016-1000221](https://insights.sbomify.com/CVE-2016-1000221/): Logstash Logs Sensitive Information (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46672 and fix it if it is affected.

What it is: CVE-2023-46672 is a high-severity vulnerability in Elastic Logstash, published on 15 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-46672 in the wild and no public exploit code.

Affected packages and fixed versions:
- logstash (Bitnami): affected from 7.12.1; fixed in 7.12.2, 8.11.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-46672/ (Markdown: https://insights.sbomify.com/CVE-2023-46672/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46672
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46672
- OSV: https://osv.dev/vulnerability/CVE-2023-46672

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-46672/
Summaries are generated and may contain mistakes; the official description above is the record.