{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-52950 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52950 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52950 is a medium-severity missing authorization vulnerability in Juniper Security Director, published on 11 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-52950 and fix it if it is affected.\n\nWhat it is: CVE-2025-52950 is a medium-severity missing authorization vulnerability in Juniper Security Director, published on 11 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-52950 in the wild and no public exploit code.\n\nAffected product: Juniper Security Director. 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-2025-52950/ (Markdown: https://insights.sbomify.com/CVE-2025-52950/index.md)","id":"CVE-2025-52950","markdown":"https://insights.sbomify.com/CVE-2025-52950/index.md","name":"CVE-2025-52950","record":{"aliases":["GHSA-f73w-2j5r-rcr4"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Juniper Security Director","requires_auth":"low_privilege","summary":"Unauthenticated attackers can read or modify sensitive resources in Juniper Security Director due to missing authorization checks on web endpoints.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"security_director","vendor":"juniper"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"A Missing Authorization vulnerability in Juniper Networks Security Director allows an unauthenticated network-based attacker to read or tamper with multiple sensitive resources via the web interface.\n\nNumerous endpoints on the Juniper Security Director appliance do not validate authorization and will deliver information to the caller that is outside their authorization level. An attacker can access data that is outside the user's authorization level. The information obtained can be used to gain access to additional information or perpetrate other attacks, impacting downstream managed devices.\n\nThis issue affects Security Director version 24.4.1.","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":"Juniper Security Director: Insufficient authorization for multiple endpoints in web interface","id":"CVE-2025-52950","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Junos OS: IPv6 firewall filter fails to match payload-protocol","id":"CVE-2025-52951"},"packages":[],"prev":{"headline":"Junos OS and Junos OS Evolved: In an EVPN environment, receipt of specifically malformed BGP update causes RPD crash","id":"CVE-2025-52949"},"products":["Juniper Security Director"],"published":"2025-07-11","related":[],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Juniper Networks"]},"summary":"Unauthenticated attackers can read or modify sensitive resources in Juniper Security Director due to missing authorization checks on web endpoints.","url":"https://insights.sbomify.com/CVE-2025-52950/"}