{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-10623 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-10623 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-10623 is a high-severity missing authorization vulnerability in Juniper Junos Space, published on 13 Oct 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-10623 and fix it if it is affected.\n\nWhat it is: CVE-2017-10623 is a high-severity missing authorization vulnerability in Juniper Junos Space, published on 13 Oct 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-10623 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-2017-10623/ (Markdown: https://insights.sbomify.com/CVE-2017-10623/index.md)","id":"CVE-2017-10623","markdown":"https://insights.sbomify.com/CVE-2017-10623/index.md","name":"CVE-2017-10623","record":{"aliases":["GHSA-gvv4-39wq-vfhg"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Junos Space","requires_auth":"low_privilege","summary":"Attackers can intercept, inject, or disrupt cluster operations in Junos Space due to lack of authentication and authorization for cluster messages.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"junos_space","vendor":"juniper"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Lack of authentication and authorization of cluster messages in Juniper Networks Junos Space may allow a man-in-the-middle type of attacker to intercept, inject or disrupt Junos Space cluster operations between two nodes. Affected releases are Juniper Networks Junos Space all versions prior to 17.1R1.","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":"Junos Space: Insufficient verification of cluster messages","id":"CVE-2017-10623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"juniper:junos_space","products":["juniper:junos_space"],"type":"missing_authorization","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Junos Space: Insufficient verification of node certificates.","id":"CVE-2017-10624"},"packages":[],"prev":{"headline":"Junos Space: Authentication bypass vulnerability","id":"CVE-2017-10622"},"products":["Junos Space"],"published":"2017-10-13","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-09-17","vendors":["Juniper Networks"]},"summary":"Attackers can intercept, inject, or disrupt cluster operations in Junos Space due to lack of authentication and authorization for cluster messages.","url":"https://insights.sbomify.com/CVE-2017-10623/"}