CVE-2020-7010 json
Cryptographic Issues in ECK
published 6y ago modified 4mo ago also GHSA-vfp4-xx6m-7vf6 , EUVD-2022-1202
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
Elastic Cloud on Kubernetes (ECK) versions prior to 1.1.0 generate passwords using a weak random number generator. If an attacker is able to determine when the current Elastic Stack cluster was deployed they may be able to more easily brute force the Elasticsearch credentials generated by ECK.
Patch / fix
- go github.com/elastic/cloud-on-k8s 1.1.0
- elastic elastic_cloud_on_kubernetes 1.1.0
Is CVE-2020-7010 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
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
1.44% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 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 |
|---|---|---|---|
| go | github.com/elastic/cloud-on-k8s | <1.1.0 |
1.1.0 |
Affected products
- Elastic Elastic Cloud on Kubernetes
Classification
- Weakness
-
- CWE-335 Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)
References
-
elastic.co
/community/security/
vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-7010
advisory
-
elastic.co
/community/security
web
Sources
- CVE List CVE-2020-7010
- GitHub Advisory GHSA-vfp4-xx6m-7vf6
- NVD CVE-2020-7010
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.