{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-8037 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8037 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8037 is a high-severity vulnerability in Cloud Foundry, published on 21 Aug 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-2017-8037 and fix it if it is affected.\n\nWhat it is: CVE-2017-8037 is a high-severity vulnerability in Cloud Foundry, published on 21 Aug 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-2017-8037 in the wild and no public exploit code.\n\nAffected product: Cloud Foundry. 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-8037/ (Markdown: https://insights.sbomify.com/CVE-2017-8037/index.md)","id":"CVE-2017-8037","markdown":"https://insights.sbomify.com/CVE-2017-8037/index.md","name":"CVE-2017-8037","record":{"aliases":["GHSA-9235-9qc9-8p4j"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Cloud Foundry CAPI","requires_auth":"none","summary":"A Space Developer can exploit an incomplete fix to access files on the Cloud Controller VM, leading to information disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"capi-release","vendor":"cloudfoundry"},{"product":"cf-release","vendor":"cloudfoundry"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Cloud Foundry Foundation CAPI-release versions after v1.6.0 and prior to v1.38.0 and cf-release versions after v244 and prior to v270, there is an incomplete fix for CVE-2017-8035. If you took steps to remediate CVE-2017-8035 you should also upgrade to fix this CVE. A carefully crafted CAPI request from a Space Developer can allow them to gain access to files on the Cloud Controller VM for that installation, aka an Information Leak / Disclosure.","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":"Information disclosure in Cloud Foundry","id":"CVE-2017-8037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in Credhub Credhub-release version 1.1.0 only","id":"CVE-2017-8038"},"packages":[],"prev":{"headline":"Code injection in Cloud Controller API CAPI-release version 1.33.0 only","id":"CVE-2017-8036"},"products":["Cloud Foundry"],"published":"2017-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.5,"headline":"Cloud Controller may allow developers to claim sensitive routes","id":"CVE-2020-5417","kev_date_added":null,"published":"2020-08-21"},{"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-08-05","vendors":["n/a"]},"summary":"A Space Developer can exploit an incomplete fix to access files on the Cloud Controller VM, leading to information disclosure.","url":"https://insights.sbomify.com/CVE-2017-8037/"}