{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-19752 exists.","fix":"No fix has been published for CVE-2019-19752 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19752 is a critical vulnerability in n/a, published on 30 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19752 and fix it if it is affected.\n\nWhat it is: CVE-2019-19752 is a critical vulnerability in n/a, published on 30 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-19752 exists.\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-2019-19752/ (Markdown: https://insights.sbomify.com/CVE-2019-19752/index.md)","id":"CVE-2019-19752","markdown":"https://insights.sbomify.com/CVE-2019-19752/index.md","name":"CVE-2019-19752","record":{"aliases":["GHSA-wgjq-hm36-r7r8"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"nvOC operating system","requires_auth":"none","summary":"nvOC ships with hardcoded SSH host keys, enabling man-in-the-middle attacks and easy device identification via Shodan.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"nvOC through 3.2 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. NOTE: as of 2019-12-01, the vendor indicated plans to fix this in the next image build.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-19752","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2019-19753"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2019-19751"},"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-25","vendors":["n/a"]},"summary":"nvOC ships with hardcoded SSH host keys, enabling man-in-the-middle attacks and easy device identification via Shodan.","url":"https://insights.sbomify.com/CVE-2019-19752/"}