{"answers":{"affected":"It affects 8 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-1561 exists.","fix":"No fix has been published for CVE-2016-1561 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-1561 is a high-severity vulnerability in n/a, published on 21 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-1561 and fix it if it is affected.\n\nWhat it is: CVE-2016-1561 is a high-severity vulnerability in n/a, published on 21 Apr 2017. 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-2016-1561 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-2016-1561/ (Markdown: https://insights.sbomify.com/CVE-2016-1561/index.md)","id":"CVE-2016-1561","markdown":"https://insights.sbomify.com/CVE-2016-1561/index.md","name":"CVE-2016-1561","record":{"aliases":["GHSA-cwr4-jwc3-f83j"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["account_takeover","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ExaGrid backup appliance","requires_auth":"none","summary":"Remote attackers can gain root SSH access to ExaGrid appliances using a hardcoded private key, leading to full system compromise.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"ex10000e_firmware","vendor":"exagrid"},{"product":"ex13000e_firmware","vendor":"exagrid"},{"product":"ex21000e_firmware","vendor":"exagrid"},{"product":"ex3000_firmware","vendor":"exagrid"},{"product":"ex32000e_firmware","vendor":"exagrid"},{"product":"ex40000e_firmware","vendor":"exagrid"},{"product":"ex5000_firmware","vendor":"exagrid"},{"product":"ex7000_firmware","vendor":"exagrid"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"ExaGrid appliances with firmware before 4.8 P26 have a default SSH public key in the authorized_keys file for root, which allows remote attackers to obtain SSH access by leveraging knowledge of a private key from another installation or a firmware image.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2016-04-07","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2016-04-07","kind":"exploitdb","ref":"41680","stars":null,"title":"ExaGrid - Known SSH Key and Default Password (Metasploit)"},{"date":"2016-04-07","kind":"metasploit","ref":"exploit/linux/ssh/exagrid_known_privkey","stars":null,"title":"ExaGrid Known SSH Key and Default Password"}],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2016-1561","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in n/a","id":"CVE-2016-1562"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2016-1560"},"products":["n/a"],"published":"2017-04-21","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2016-1560","kev_date_added":null,"published":"2017-04-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can gain root SSH access to ExaGrid appliances using a hardcoded private key, leading to full system compromise.","url":"https://insights.sbomify.com/CVE-2016-1561/"}