{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-4927 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-4927 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-4927 is a high-severity vulnerability in Juniper Junos Space, published on 20 Mar 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-4927 and fix it if it is affected.\n\nWhat it is: CVE-2016-4927 is a high-severity vulnerability in Juniper Junos Space, published on 20 Mar 2017. 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-2016-4927 in the wild and no public exploit code.\n\nAffected product: Juniper Junos Space. 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-4927/ (Markdown: https://insights.sbomify.com/CVE-2016-4927/index.md)","id":"CVE-2016-4927","markdown":"https://insights.sbomify.com/CVE-2016-4927/index.md","name":"CVE-2016-4927","record":{"aliases":["GHSA-gr4g-xqg8-fh3v"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Junos Space","requires_auth":"none","summary":"Insufficient SSH key validation in Junos Space allows man-in-the-middle attacks during communication with managed devices.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"junos_space","vendor":"juniper"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Insufficient validation of SSH keys in Junos Space before 15.2R2 allows man-in-the-middle (MITM) type of attacks while a Space device is communicating with managed devices.","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":"Security feature bypass in n/a","id":"CVE-2016-4927","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"juniper:junos_space","products":["juniper:junos_space"],"type":"security_feature_bypass","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2016-4928"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2016-4926"},"products":["n/a"],"published":"2017-03-20","related":[{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2014-3412","kev_date_added":null,"published":"2014-05-20"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2014-3413","kev_date_added":null,"published":"2018-04-05"},{"cvss_score":9.8,"headline":"Junos Space: privilege escalation vulnerabilities in Junos Space","id":"CVE-2016-1265","kev_date_added":null,"published":"2017-10-13"},{"cvss_score":9.8,"headline":"Junos Space: Authentication bypass vulnerability","id":"CVE-2017-10622","kev_date_added":null,"published":"2017-10-13"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2016-4926","kev_date_added":null,"published":"2017-03-20"},{"cvss_score":9.4,"headline":"Junos Space: Stored cross-site scripting vulnerability in web application","id":"CVE-2025-59978","kev_date_added":null,"published":"2025-10-09"},{"cvss_score":8.8,"headline":"Junos Space: Reflected Cross-site Scripting vulnerability in OpenNMS","id":"CVE-2018-0046","kev_date_added":null,"published":"2018-10-10"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Insufficient SSH key validation in Junos Space allows man-in-the-middle attacks during communication with managed devices.","url":"https://insights.sbomify.com/CVE-2016-4927/"}