{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-5417 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-5417 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-5417 is a high-severity missing authorization vulnerability in Cloud Foundry CAPI, published on 21 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-5417 and fix it if it is affected.\n\nWhat it is: CVE-2020-5417 is a high-severity missing authorization vulnerability in Cloud Foundry CAPI, published on 21 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-5417 in the wild and no public exploit code.\n\nAffected product: Cloud Foundry CAPI. 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-2020-5417/ (Markdown: https://insights.sbomify.com/CVE-2020-5417/index.md)","id":"CVE-2020-5417","markdown":"https://insights.sbomify.com/CVE-2020-5417/index.md","name":"CVE-2020-5417","record":{"aliases":["GHSA-jq2q-gqc9-53g3"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Cloud Foundry CAPI","requires_auth":"low_privilege","summary":"Developers can claim sensitive system routes in Cloud Foundry, allowing their apps to intercept system component requests.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"pivotal","cpe":[{"product":"capi-release","vendor":"cloudfoundry"},{"product":"cf-deployment","vendor":"cloudfoundry"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Cloud Foundry CAPI (Cloud Controller), versions prior to 1.97.0, when used in a deployment where an app domain is also the system domain (which is true in the default CF Deployment manifest), were vulnerable to developers maliciously or accidentally claiming certain sensitive routes, potentially resulting in the developer's app handling some requests that were expected to go to certain system components.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cloud Controller may allow developers to claim sensitive routes","id":"CVE-2020-5417","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cloud Controller allows users with no roles to list droplets","id":"CVE-2020-5418"},"packages":[],"prev":{"headline":"CF clusters with NGINX in front of them may be vulnerable to DoS","id":"CVE-2020-5416"},"products":["CAPI","CF Deployment"],"published":"2020-08-21","related":[{"cvss_score":8.8,"headline":"Auth bypass in Cloud Controller","id":"CVE-2018-1195","kev_date_added":null,"published":"2018-03-19"},{"cvss_score":8.1,"headline":"Missing authorization in Cloud Controller API","id":"CVE-2023-20881","kev_date_added":null,"published":"2023-05-19"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2018-1266","kev_date_added":null,"published":"2018-03-27"},{"cvss_score":8,"headline":"Cloud Controller logs environment variables from app manifests","id":"CVE-2020-5400","kev_date_added":null,"published":"2020-02-27"},{"cvss_score":7.8,"headline":"Path traversal in Cloud Controller API CAPI-release versions prior to v1.35.0 and cf-release versions prior to v268","id":"CVE-2017-8033","kev_date_added":null,"published":"2017-07-25"},{"cvss_score":7.8,"headline":"Code injection in Cloud Controller API CAPI-release version 1.33.0 only","id":"CVE-2017-8036","kev_date_added":null,"published":"2017-07-24"}],"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-16","vendors":["Cloud Foundry"]},"summary":"Developers can claim sensitive system routes in Cloud Foundry, allowing their apps to intercept system component requests.","url":"https://insights.sbomify.com/CVE-2020-5417/"}