{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-45617 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-45617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-45617 is a high-severity missing authorization vulnerability in n/a, published on 5 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-45617 and fix it if it is affected.\n\nWhat it is: CVE-2025-45617 is a high-severity missing authorization vulnerability in n/a, published on 5 May 2025. 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-2025-45617 in the wild and no public exploit code.\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-2025-45617/ (Markdown: https://insights.sbomify.com/CVE-2025-45617/index.md)","id":"CVE-2025-45617","markdown":"https://insights.sbomify.com/CVE-2025-45617/index.md","name":"CVE-2025-45617","record":{"aliases":["GHSA-5pv4-5wmq-2pxg"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"production_ssm application","requires_auth":"none","summary":"Attackers can access sensitive information in production_ssm due to incorrect access control on the user list endpoint.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"production_ssm","vendor":"megagao"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Incorrect access control in the component /user/list of production_ssm v0.0.1-SNAPSHOT allows attackers to access sensitive information via a crafted payload.","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":"Missing authorization in n/a","id":"CVE-2025-45617","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":"Missing authorization in n/a","id":"CVE-2025-45618"},"packages":[],"prev":{"headline":"BRCC Incorrect Access Control vulnerability","id":"CVE-2025-45616"},"products":["n/a"],"published":"2025-05-05","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":"partial"},"state":"PUBLISHED","updated":"2025-05-06","vendors":["n/a"]},"summary":"Attackers can access sensitive information in production_ssm due to incorrect access control on the user list endpoint.","url":"https://insights.sbomify.com/CVE-2025-45617/"}