{"answers":{"affected":"2 open source packages ship an affected version, including github.com/elastic/cloud-on-k8s. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7010 in the wild and no public exploit code.","fix":"Upgrade github.com/elastic/cloud-on-k8s to 1.1.0 or later.","what":"CVE-2020-7010 is a high-severity vulnerability in Elastic Cloud on Kubernetes, published on 3 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-7010 and fix it if it is affected.\n\nWhat it is: CVE-2020-7010 is a high-severity vulnerability in Elastic Cloud on Kubernetes, published on 3 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-7010 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/elastic/cloud-on-k8s (Go): affected all versions; fixed in 1.1.0\n- github.com/elastic/cloud-on-k8s (Go): affected all versions; fixed in 1.1.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-7010/ (Markdown: https://insights.sbomify.com/CVE-2020-7010/index.md)","id":"CVE-2020-7010","markdown":"https://insights.sbomify.com/CVE-2020-7010/index.md","name":"CVE-2020-7010","record":{"aliases":["GHSA-vfp4-xx6m-7vf6"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Elastic Cloud on Kubernetes","requires_auth":"none","summary":"Weak random number generation in ECK allows attackers to brute force Elasticsearch credentials if deployment time is known.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"elastic_cloud_on_kubernetes","vendor":"elastic"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-335","name":"Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Cryptographic Issues in ECK","id":"CVE-2020-7010","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"weak_cryptography","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"Cross-site scripting in Elastic App Search","id":"CVE-2020-7011"},"packages":[{"ecosystem":"Go","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"github.com/elastic/cloud-on-k8s","purl":null,"source":"GHSA-vfp4-xx6m-7vf6"},{"ecosystem":"Go","fixed":["1.1.0"],"introduced":["0"],"last_affected":[],"package":"github.com/elastic/cloud-on-k8s","purl":"pkg:golang/github.com/elastic/cloud-on-k8s","source":"GHSA-vfp4-xx6m-7vf6"}],"prev":{"headline":"Improper Privilege Management in Elasticsearch","id":"CVE-2020-7009"},"products":["Elastic Cloud on Kubernetes"],"published":"2020-06-03","related":[{"cvss_score":6.5,"headline":"Unintended Proxy or Intermediary in Elastic Cloud on Kubernetes Leading to Cross-Namespace Secret Disclosure","id":"CVE-2026-72640","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":6.5,"headline":"Information disclosure in Eck Operator","id":"CVE-2026-72648","kev_date_added":null,"published":"2026-08-13"},{"cvss_score":5.4,"headline":"Incorrect Authorization in Elastic Cloud on Kubernetes Leading to Unauthorized Modification of Data","id":"CVE-2026-78609","kev_date_added":null,"published":"2026-09-02"},{"cvss_score":5.3,"headline":"Elastic Cloud on Kubernetes (ECK) secret token configuration issue","id":"CVE-2023-31416","kev_date_added":null,"published":"2023-10-26"},{"cvss_score":3.5,"headline":"Incomplete Cleanup in Elastic Cloud on Kubernetes Leading to Unauthorized Cross-Namespace Credential Retention","id":"CVE-2026-78600","kev_date_added":null,"published":"2026-09-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-18","vendors":["Elastic"]},"summary":"Weak random number generation in ECK allows attackers to brute force Elasticsearch credentials if deployment time is known.","url":"https://insights.sbomify.com/CVE-2020-7010/"}