cve.bz

CVE-2023-31417 elastic elasticsearch

4.4 mediumEPSS 0.2%Fix available

Medium (4.4) in elastic elasticsearch. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in org.elasticsearch:elasticsearch 7.17.13, 8.9.2.

On this page
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.

Severity

CVSS 3.1

4.4 medium
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-31417 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-31417?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-31417?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-31417 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Elasticsearchfrom 7.0.0 before 7.17.12
Elasticsearchfrom 8.0.0 before 8.9.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-99pc-69q9-jxf2Mavenorg.elasticsearch:elasticsearch>=7.0.0 <7.17.137.17.13
GHSA-99pc-69q9-jxf2Mavenorg.elasticsearch:elasticsearch>=8.0.0 <8.9.28.9.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu16.04:LTSelasticsearchno fix listedUBUNTU-CVE-2023-31417

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The 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. Hence, the impact is set to Moderate.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Please update the affected package as soon as possible.

ProductPackageStateAdvisory
Logging Subsystem for Red Hat OpenShiftopenshift-logging/elasticsearch6-rhel8Not affected
Red Hat OpenShift Container Platform 3.11openshift3/ose-logging-elasticsearch5Out of support scope
Red Hat OpenShift Container Platform 4elasticsearchWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-31417.

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON