{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2020-5200 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-5200 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-5200 is a medium-severity vulnerability in n/a, published on 30 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-5200 and fix it if it is affected.\n\nWhat it is: CVE-2020-5200 is a medium-severity vulnerability in n/a, published on 30 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-5200 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-5200/ (Markdown: https://insights.sbomify.com/CVE-2020-5200/index.md)","id":"CVE-2020-5200","markdown":"https://insights.sbomify.com/CVE-2020-5200/index.md","name":"CVE-2020-5200","record":{"aliases":["GHSA-x82q-r52r-c4wr"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Minerbabe server","requires_auth":"none","summary":"Minerbabe ships with hardcoded SSH host keys, enabling man-in-the-middle attacks and trivial identification of public nodes.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[],"description":"Minerbabe through V4.16 ships with SSH host keys baked into the installation image, which allows man-in-the-middle attacks and makes identification of all public IPv4 nodes trivial with Shodan.io.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-5200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-5202"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-5197"},"products":["n/a"],"published":"2024-04-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-04","vendors":["n/a"]},"summary":"Minerbabe ships with hardcoded SSH host keys, enabling man-in-the-middle attacks and trivial identification of public nodes.","url":"https://insights.sbomify.com/CVE-2020-5200/"}