Bug 2237927 (CVE-2023-31417)
| Summary: | CVE-2023-31417 elasticsearch: Sensitive information in audit logs | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | Zack Miele <zmiele> |
| Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
| Status: | NEW --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | dfreiber, jburrell, jcantril, rogbas, vkumar |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | elasticsearch 7.17.13, elasticsearch 8.9.2 | Doc Type: | If docs needed, set a value |
| Doc Text: |
A flaw was found in the Elasticsearch package. Elasticsearch filters out sensitive information and credentials before logging into the audit log. It was found that this filtering was not applied when requests to Elasticsearch use certain deprecated URIs for APIs. As a result, sensitive information such as passwords and tokens might be printed in cleartext in Elasticsearch audit logs.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2237926 | ||
Elasticsearch Insertion of sensitive information in audit logs (ESA-2023-12) 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. The _xpack/security APIs have been deprecated in Elasticsearch 7.x and were entirely removed in 8.0.0 and later. The only way for a client to use them in Elasticsearch 8.0.0 and later is to provide the Accept: application/json; compatible-with=7 header. Elasticsearch official clients do not use these deprecated APIs. The list of affected, deprecated APIs, is the following * POST /_xpack/security/user/{username} * PUT /_xpack/security/user/{username} * PUT /_xpack/security/user/{username}/_password * POST /_xpack/security/user/{username}/_password * PUT /_xpack/security/user/_password * POST /_xpack/security/user/_password * POST /_xpack/security/oauth2/token * DELETE /_xpack/security/oauth2/token * POST /_xpack/security/saml/authenticate Affected Versions: Elasticsearch versions from 7.0.0 up to 7.17.12 and from 8.0.0 up to 8.9.1 Solutions and Mitigations: The issue is resolved in version 7.17.13 and 8.9.2 CVSSv3.1: 4.1(Medium) AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N CVE ID: CVE-2023-31417 1 post - 1 participant Read full topic