Elasticsearch versions before 7.10.0 and 6.8.14 have an information disclosure issue when audit logging and the emit_request_body option is enabled. The Elasticsearch audit log could contain sensitive information such as password hashes or authentication tokens. This could allow an Elasticsearch administrator to view these details.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Elasticsearch | Elastic | * | 6.8.14 (excluding) |
| Elasticsearch | Elastic | 7.0.0 (including) | 7.10.0 (excluding) |
| Elasticsearch | Ubuntu | esm-apps/xenial | * |
| Elasticsearch | Ubuntu | trusty | * |
| Elasticsearch | Ubuntu | xenial | * |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: