{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-4970 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-4970 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-4970 is a medium-severity authentication bypass vulnerability in Cloud Foundry, published on 13 Jun 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-4970 and fix it if it is affected.\n\nWhat it is: CVE-2017-4970 is a medium-severity authentication bypass vulnerability in Cloud Foundry, published on 13 Jun 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-4970 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-4970/ (Markdown: https://insights.sbomify.com/CVE-2017-4970/index.md)","id":"CVE-2017-4970","markdown":"https://insights.sbomify.com/CVE-2017-4970/index.md","name":"CVE-2017-4970","record":{"aliases":["GHSA-xvcr-4h4q-m7m8"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Cloud Foundry buildpack","requires_auth":"none","summary":"A regression in the Staticfile buildpack disables basic authentication for misconfigured applications, allowing unauthorized access to protected resources.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"cf-release","vendor":"cloudfoundry"},{"product":"staticfile_buildpack","vendor":"cloudfoundry"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[],"description":"An issue was discovered in Cloud Foundry Foundation cf-release v255 and Staticfile buildpack versions v1.4.0 - v1.4.3. A regression introduced in the Static file build pack causes the Staticfile.auth configuration to be ignored when the Static file file is not present in the application root. Applications containing a Staticfile.auth file but not a Static file had their basic auth turned off when an operator upgraded the Static file build pack in the foundation to one of the vulnerable versions. Note that Static file applications without a Static file are technically misconfigured, and will not successfully detect unless the Static file build pack is explicitly specified.","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":"Auth bypass in Cloud Foundry","id":"CVE-2017-4970","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Insecure Default Initialization of Resource in Pivotal Spring Web Flow","id":"CVE-2017-4971"},"packages":[],"prev":{"headline":"Business logic in Cloud Foundry Cloud Controller cf-release versions prior to v255","id":"CVE-2017-4969"},"products":["Cloud Foundry"],"published":"2017-06-13","related":[{"cvss_score":9.8,"headline":"Cloud Foundry Runtime Insufficient Session Expiration vulnerability","id":"CVE-2015-5171","kev_date_added":null,"published":"2017-10-24"},{"cvss_score":9.8,"headline":"Cloud Foundry Runtime has Weak Password Recovery Mechanism for Forgotten Password","id":"CVE-2015-5172","kev_date_added":null,"published":"2017-10-24"},{"cvss_score":9.8,"headline":"Auth bypass in Cloud Foundry","id":"CVE-2016-8218","kev_date_added":null,"published":"2017-06-13"},{"cvss_score":9.8,"headline":"Cloud Foundry UAA privilege escalation with user invitations","id":"CVE-2017-4992","kev_date_added":null,"published":"2017-06-13"},{"cvss_score":9.6,"headline":"Information disclosure in n/a","id":"CVE-2016-6658","kev_date_added":null,"published":"2018-03-29"},{"cvss_score":8.8,"headline":"Cloud Foundry Runtime Cross-Site Request Forgery vulnerability","id":"CVE-2015-5170","kev_date_added":null,"published":"2017-10-24"},{"cvss_score":8.8,"headline":"Information disclosure in n/a","id":"CVE-2015-5173","kev_date_added":null,"published":"2017-10-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":"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 regression in the Staticfile buildpack disables basic authentication for misconfigured applications, allowing unauthorized access to protected resources.","url":"https://insights.sbomify.com/CVE-2017-4970/"}