Elastic Logstash 7.12.1
Approved changes feed: RSS · Atom
cpe:2.3:a:elastic:logstash:7.12.1:*:*:*:*:*:*:*
part: a version: 7.12.1 update: *
| Vendor | Elastic (1d0b8d2a-fd47-5b20-b005-34326f9bd037) |
|---|---|
| Product | Logstash (583fe5fc-dd43-51b3-bf4d-e6399cb079bf) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/elastic/logstash |
purl2cpe | 2026-06-01 10:15:14.205541 |
pkg:sourceforge/logstash.mirror |
purl2cpe | 2026-06-01 10:15:14.205542 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-46672 |
vulnerable | 2026-06-03 14:53:10.323717 |
Logstash Insertion of Sensitive Information into Log File
HIGH (8.4)
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.
Published: 2023-11-15T08:05:26.561Z
Updated: 2025-02-13T17:14:31.789Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.