Information Exposure The advisory has been revoked - it doesn't affect any version of package elasticsearch (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Information Exposure vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-ELASTICSEARCH-5892782
- published12 Sept 2023
- disclosed6 Sept 2023
- creditUnknown
Introduced: 6 Sep 2023
CVE-2023-31417 (opens in a new tab)How to fix?
There is no fixed version for elasticsearch.
Amendment
This was deemed not a vulnerability.
Overview
elasticsearch is a The official low-level Elasticsearch client for Node.js and the browser.
Affected versions of this package are vulnerable to Information Exposure due to not filtering out sensitive information and credentials before logging to the audit log 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:
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 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
This issue was revoked as according to the vendor, Elasticsearch official clients do not use these deprecated APIs.