{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2016-2165 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-2165 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-2165 is a medium-severity cross-site scripting vulnerability in Pivotal Cloud Foundry, published on 25 May 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2016-2165 and fix it if it is affected.\n\nWhat it is: CVE-2016-2165 is a medium-severity cross-site scripting vulnerability in Pivotal Cloud Foundry, published on 25 May 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2016-2165 in the wild and no public exploit code.\n\nAffected product: Pivotal 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-2016-2165/ (Markdown: https://insights.sbomify.com/CVE-2016-2165/index.md)","id":"CVE-2016-2165","markdown":"https://insights.sbomify.com/CVE-2016-2165/index.md","name":"CVE-2016-2165","record":{"aliases":["GHSA-p5pc-pcfq-64rw"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Cloud Foundry","requires_auth":"none","summary":"Attackers can inject malicious scripts into 404 error responses via unsanitized URL paths in Cloud Foundry Loggregator Traffic Controller.","user_interaction":"required","vuln_class":"xss"},"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":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The Loggregator Traffic Controller endpoints in cf-release v231 and lower, Pivotal Elastic Runtime versions prior to 1.5.19 AND 1.6.x versions prior to 1.6.20 are not cleansing request URL paths when they are invalid and are returning them in the 404 response. This could allow malicious scripts to be written directly into the 404 response.","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":"Cross-site scripting in Cloud Foundry","id":"CVE-2016-2165","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2016"},"n_packages":0,"n_references":1,"next":{"headline":"Moderate severity vulnerability that affects org.apache.qpid:proton-j","id":"CVE-2016-2166"},"packages":[],"prev":{"headline":"Apache OpenMeetings allows remote attackers to read arbitrary files by attempting to upload a file","id":"CVE-2016-2164"},"products":["Cloud Foundry"],"published":"2017-05-25","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":"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":["Pivotal"]},"summary":"Attackers can inject malicious scripts into 404 error responses via unsanitized URL paths in Cloud Foundry Loggregator Traffic Controller.","url":"https://insights.sbomify.com/CVE-2016-2165/"}