{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-6658 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6658 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6658 is a critical vulnerability in n/a, published on 29 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-6658 and fix it if it is affected.\n\nWhat it is: CVE-2016-6658 is a critical vulnerability in n/a, published on 29 Mar 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-6658 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-2016-6658/ (Markdown: https://insights.sbomify.com/CVE-2016-6658/index.md)","id":"CVE-2016-6658","markdown":"https://insights.sbomify.com/CVE-2016-6658/index.md","name":"CVE-2016-6658","record":{"aliases":["GHSA-5559-gfmr-27qq"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Cloud Foundry","requires_auth":"low_privilege","summary":"Privileged operators can view unencrypted credentials in buildpack URLs, exposing sensitive authentication data stored in the Cloud Controller database.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"cf-release","vendor":"cloudfoundry"},{"product":"cloud_foundry_elastic_runtime","vendor":"pivotal_software"}],"cvss":{"score":9.6,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Applications in cf-release before 245 can be configured and pushed with a user-provided custom buildpack using a URL pointing to the buildpack. Although it is not recommended, a user can specify a credential in the URL (basic auth or OAuth) to access the buildpack through the CLI. For example, the user could include a GitHub username and password in the URL to access a private repo. Because the URL to access the buildpack is stored unencrypted, an operator with privileged access to the Cloud Controller database could view these credentials.","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 n/a","id":"CVE-2016-6658","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Cloud Foundry v247 and earlier and UAA v3.9.2 \u0026 earlier and UAA bosh (uaa-release) v23 \u0026 earlier","id":"CVE-2016-6659"},"packages":[],"prev":{"headline":"Open redirect in PCF Elastic Runtime 1.8.x versions prior to 1.8.12 and PCF Ops Manager 1.7.x versions prior to 1.7.18 and 1.8.x versions prior to 1.8.10","id":"CVE-2016-6657"},"products":["n/a"],"published":"2018-03-29","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":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":"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-06","vendors":["n/a"]},"summary":"Privileged operators can view unencrypted credentials in buildpack URLs, exposing sensitive authentication data stored in the Cloud Controller database.","url":"https://insights.sbomify.com/CVE-2016-6658/"}