BIT-elasticsearch-2023-31417

    Dashboard / Vulnerabilities / BIT-elasticsearch-2023-31417

    BIT-elasticsearch-2023-31417

    Published: 6 Mar 2024Last Modified: 8 Sept 2026

    Summary: Elasticsearch Insertion of sensitive information in audit logs

    Details: 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.

    References: https://discuss.elastic.co/t/elasticsearch-8-9-2-and-7-17-13-security-update/342479, https://security.netapp.com/advisory/ntap-20231130-0006/, https://www.elastic.co/community/security, https://nvd.nist.gov/vuln/detail/CVE-2023-31417

    Affected packages

    Package

    Name: elasticsearch

    Purl: pkg:bitnami/elasticsearch

    Affected ranges

    Type: SEMVER

    Events:

    Introduced- 7.0.0
    Fixed -7.17.13

    Affected versions

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High