4.1
Moyenne
CVE-2023-31417 Elasticsearch generally filters out sensitive information and credentials before logging to the audit log
Description
Elasticsearch generally filters out sensitive information and credentials before logging to the audit log. It was found that this filtering was not applied when requests to Elasticsearch use certain deprecated URIs for APIs. The impact of this flaw is that sensitive information such as passwords and tokens might be printed in cleartext in Elasticsearch audit logs. Note that audit logging is disabled by default and needs to be explicitly enabled and even when audit logging is enabled, request bodies that could contain sensitive information are not printed to the audit log unless explicitly configured.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| Elasticsearch 8.0 | 8.0.0 → < 8.9.1 | 8.9.1 |
| Elasticsearch 7.0 | 7.0.0 → < 7.17.12 | 7.17.12 |
Autres CVE de Elasticsearch
Les 91 CVE de Elasticsearch →
CVE-2026-115715
Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to denial of service via a…
6.5
Moyenne
CVE-2026-115710
Use of Cache Containing Sensitive Information (CWE-524) in Elasticsearch can lead to information disclosure and…
4.2
Moyenne
CVE-2026-115298
Incorrect Authorization (CWE-863) in Elasticsearch can lead to information disclosure via Accessing Functionality Not…
4.3
Moyenne
CVE-2026-115290
Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via Serialized Data with Nested Payloads…
7.5
Élevée