Elasticsearch Insertion of sensitive information in audit logs
CVE-2023-31417
7.5HIGH
Summary
Elasticsearch has a flaw that permits the exposure of sensitive information, such as passwords and tokens, in audit logs under specific conditions. While Elasticsearch is designed to filter out sensitive data before logging, this functionality fails with certain deprecated API URIs. Audit logging, which is disabled by default, must be enabled explicitly for this issue to become a concern. Even when logging is active, sensitive request bodies may only appear in logs if specifically configured, hence organizations need to be aware of these settings to prevent inadvertent data leaks.
Affected Version(s)
Elasticsearch 7.0.0 < 7.17.12
Elasticsearch 8.0.0 < 8.9.1
References
CVSS V3.1
Score:
7.5
Severity:
HIGH
Confidentiality:
High
Integrity:
None
Availability:
High
Attack Vector:
Network
Attack Complexity:
Low
Privileges Required:
None
User Interaction:
None
Scope:
Unchanged
Timeline
Vulnerability published
Vulnerability Reserved