CVE-2024-23444 json
Elasticsearch elasticsearch-certutil csr fails to encrypt private key
published 2y ago modified 2mo ago also BIT-elasticsearch-2024-23444 , EUVD-2024-2271 , GHSA-5v8f-xx9m-wj44
- cvss
- 4.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
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.
Patch / fix
- maven org.elasticsearch:elasticsearch 7.17.23, 8.13.0
- bitnami elasticsearch 7.17.23, 8.13.0
- Elastic Elasticsearch 7.17.23, 8.13.0
- github.com/elastic/elasticsearch@07296d5 commit
- github.com/elastic/elasticsearch@321c4e1 commit
- github.com/elastic/elasticsearch@bb1edda commit
- github.com/elastic/elasticsearch#106105 pull request
- github.com/elastic/elasticsearch#109834 pull request
Is CVE-2024-23444 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.elasticsearch:elasticsearch | >=8.0.0-alpha1, <8.13.0 <7.17.23 |
8.13.0 7.17.23 |
| bitnami | elasticsearch | <7.17.23 >=8.0.0, <8.13.0 |
7.17.23 8.13.0 |
Affected products
- Elastic Elasticsearch
Classification
- Weakness
-
- CWE-311 Missing Encryption of Sensitive Data
References
-
github.com
/elastic/elasticsearch/pull/106105
web
-
github.com
/elastic/elasticsearch/pull/109834
web
-
github.com
/elastic/elasticsearch/commit/07296d596a1dee24730e33ad40b6726f70c6fc23
web
-
github.com
/elastic/elasticsearch/commit/321c4e1e6b738bf80faa41dbb9881489a4ab44e5
web
-
github.com
/elastic/elasticsearch/commit/bb1eddada3678257838b0590090ff9eb68acaa1b
web
-
discuss.elastic.co
/t/elasticsearch-8-13-0-7-17-23-security-update-esa-2024-12/364157
web, vendor-advisory, advisory
-
security.netapp.com
/advisory/ntap-20250404-0001/
web
-
nvd.nist.gov
/vuln/detail/CVE-2024-23444
advisory, web
-
github.com
/elastic/elasticsearch
package
-
security.netapp.com
/advisory/ntap-20250404-0001
web
Sources
- CVE List CVE-2024-23444
- GitHub Advisory GHSA-5v8f-xx9m-wj44
- NVD CVE-2024-23444
- OSV BIT-elasticsearch-2024-23444
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.