CVE-2024-23444GHSA-5V8F-XX9M-WJ44BIT-ELASTICSEARCH-2024-23444
Elasticsearch elasticsearch-certutil csr fails to encrypt private key
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.17.23, 8.13.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Elastic Elasticsearch
From 7.x · fixed in 7.17.23; From 8.x · fixed in 8.13.0
- org.elasticsearch:elasticsearchMaven
From 8.0.0-alpha1 · fixed in 8.13.0
- org.elasticsearch:elasticsearchMaven
fixed in 7.17.23