CVE-20XX-?
agent?

CVE-2023-31417

4.1 MEDIUM 0.2% exploit odds Fix listed

What it is

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.

At a glance

Exploitability
Can be exploited locally on the machine with an admin-level account. High risk of data exposure.
Exploit odds
0.2% chance of exploitation in the next 30 days (EPSS).
Fix
A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

  1. PublishedDisclosed publicly on CVE.org and NVD
  2. Last updatedMost recent change to the record

Why it ranks here

Details

Published
Last modified
Exploit probability
0.2% · EPSS, next 30 days
Weakness
CWE-532 · Secrets in logs
Record status
Modified

Affected

Attack profile CVSS 3.1 · 4.1

Attack vector
Local
Complexity
High
Privileges needed
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
Raw vector

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2023-31417.md and follow it. Check whether this project is affected by CVE-2023-31417. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Meme: I wake up, CVE-2023-31417
Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record