CVE-2023-31417

mediumPriorität · verfolgen · 18EPSS 0.002 · 15. PerzentilDEEURUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.24% (15th) EPSS
CVSS 4.4 · medium
Is it mine?
10 products
Prüfe deine Angriffsfläche
Who says so?
6 sources
cnnvd · enisa_euvd · fstec_bdu · osv

EPSS · bewertet 2026-10-27

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.

01

cvss

Technischer Schweregrad, 0–10. Eine Zeile je Quelle.

4.4
010

Basiswert 0–10 · höher = schwerwiegender · Vektor überfahren zum Auflösen

v3.14.4mediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:Nprimary · NVD / NIST USAusnutzbarkeit 0.8 · Auswirkung 3.6
v3.14.1mediumAV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:Nsecondary · FSTEC (BDU) RU
v3.14.1mediumCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:Nsecondary · ENISA EU
v3.14.1mediumCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:Nsecondary · security@elastic.coAusnutzbarkeit 0.5 · Auswirkung 3.6
v3.14.1mediumCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:Nsecondary · OSV
v3.14.1mediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N/E:Usecondary · CVSS-BT (t0sche)
02

schwächen

Die CWE-Schwächeklassen, zu denen dies gehört.

03

betroffene Produkte (10)

Betroffene Produkte und Versionsbereiche.

04

Advisories (3)

Hersteller- und Ökosystem-Meldungen dazu.

  • WID-SEC-W-2023-2276Elasticsearch: Schwachstelle ermöglicht Offenlegung von InformationenDeutsch2023-09-06csaf · cert_bundDE

    Ein lokaler Angreifer kann eine Schwachstelle in Elasticsearch ausnutzen, um Informationen offenzulegen.

  • GHSA-99pc-69q9-jxf2Elasticsearch allows insertion of sensitive information into log files when using deprecated URIs2023-10-26ghsa · osvUS

    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. 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`

  • BIT-elasticsearch-2023-31417Elasticsearch Insertion of sensitive information in audit logs2024-03-06vendor · osvUS

    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.

05

auch bekannt als (6)

Weitere Namen und Kennungen dieser Entität.

06

quellen

Welche Quellen diesen Datensatz belegen und wann.

veröffentlicht 2023-10-26geändert 2026-06-17
08

Referenzen (10)

Externe Belege — Patches, Meldungen, Analysen.

scry

Angreifer nutzen Schwachstellen wie diese gegen im Internet exponierte Dienste aus. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.

Kostenloser Scan