CVE-2023-46672

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-11-15 08:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 06:31 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 8.4 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-11-15 08:15 UTC

Last modified

2026-06-17 06:31 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-532 · Secrets in logs

Record status

Modified

Affected

• Elastic Logstash < 8.11.1
• Elastic Logstash 7.12.1

Attack profile CVSS 3.1 · 8.4

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2023-46672.md and follow it. Check whether this project is affected by CVE-2023-46672. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge