CVE-2023-46672 json
Logstash Insertion of Sensitive Information into Log File
published 2023-11-15 2 y ago modified 2026-09-10 59 d ago also BIT-logstash-2023-46672 , EUVD-2023-50863
- cvss
- 8.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami logstash 7.12.2, 8.11.1
- Elastic Logstash 8.11.1
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.4 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 8.4 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | logstash | >=7.12.1, <7.12.2 >=8.10.0, <8.11.1 |
7.12.2 8.11.1 |
Affected products
- Elastic Logstash
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
References
-
elastic.co
/community/security
vendor-advisory, advisory
-
discuss.elastic.co
/t/logstash-8-11-1-security-update-esa-2023-26/347191
release-notes, article
-
security.netapp.com
/advisory/ntap-20240125-0002/
web
-
security.netapp.com
/advisory/ntap-20240229-0001/
web
-
nvd.nist.gov
/vuln/detail/CVE-2023-46672
web
Sources
- CVE List CVE-2023-46672
- NVD CVE-2023-46672
- OSV BIT-logstash-2023-46672
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.