{"answers":{"affected":"2 open source packages ship an affected version, including keystone. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16570 in the wild and no public exploit code.","fix":"Upgrade keystone to 4.0.0-beta.7 or later.","what":"CVE-2017-16570 is a high-severity vulnerability in n/a, published on 6 Nov 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-2017-16570 and fix it if it is affected.\n\nWhat it is: CVE-2017-16570 is a high-severity vulnerability in n/a, published on 6 Nov 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-2017-16570 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- keystone (npm): affected all versions; fixed in 4.0.0-beta.7\n- keystone (npm): affected all versions; fixed in 4.0.0-beta.7\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-16570/ (Markdown: https://insights.sbomify.com/CVE-2017-16570/index.md)","id":"CVE-2017-16570","markdown":"https://insights.sbomify.com/CVE-2017-16570/index.md","name":"CVE-2017-16570","record":{"aliases":["GHSA-q43c-g2g7-6gxj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"KeystoneJS CMS","requires_auth":"none","summary":"KeystoneJS fails to validate CSRF tokens, allowing attackers to bypass protection and perform unauthorized actions on behalf of users.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"keystone","vendor":"keystonejs"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"KeystoneJS before 4.0.0-beta.7 allows application-wide CSRF bypass by removing the CSRF parameter and value, aka SecureLayer7 issue number SL7_KEYJS_03. In other words, it fails to reject requests that lack an x-csrf-token header.","ecosystems":["npm"],"exploits":{"exploitdb":1,"first_seen":"2018-01-28","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-01-28","kind":"exploitdb","ref":"43922","stars":null,"title":"KeystoneJS \u003c 4.0.0-beta.7 - Cross-Site Request Forgery"}],"tier":"poc_unverified"},"has_fix":true,"headline":"Cross-Site Request Forgery (CSRF) in keystone","id":"CVE-2017-16570","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"csrf","year":"2017"},"n_packages":2,"n_references":4,"next":{"headline":"Memory corruption in Foxit Reader","id":"CVE-2017-16571"},"packages":[{"ecosystem":"npm","fixed":["4.0.0-beta.7"],"introduced":["0"],"last_affected":[],"package":"keystone","purl":null,"source":"GHSA-q43c-g2g7-6gxj"},{"ecosystem":"npm","fixed":["4.0.0-beta.7"],"introduced":["0"],"last_affected":[],"package":"keystone","purl":"pkg:npm/keystone","source":"GHSA-q43c-g2g7-6gxj"}],"prev":{"headline":"Open redirect in n/a","id":"CVE-2017-16569"},"products":["n/a"],"published":"2017-11-06","related":[{"cvss_score":9.8,"headline":"NODE_ENV in Keystone defaults to development with esbuild","id":"CVE-2022-39382","kev_date_added":null,"published":"2022-11-03"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-29354","kev_date_added":null,"published":"2022-05-16"},{"cvss_score":9.1,"headline":"@keystone-6/core vulnerable to field-level access-control bypass for multiselect field","id":"CVE-2022-39322","kev_date_added":null,"published":"2022-10-25"},{"cvss_score":8.8,"headline":"Keystone is vulnerable to CSV injection","id":"CVE-2017-15879","kev_date_added":null,"published":"2017-10-24"},{"cvss_score":7.5,"headline":"Authentication Weakness in keystone","id":"CVE-2015-9240","kev_date_added":null,"published":"2018-05-29"},{"cvss_score":7.1,"headline":"Cross-site Scripting (XSS) - Reflected in keystonejs/keystone","id":"CVE-2022-0087","kev_date_added":null,"published":"2022-01-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"KeystoneJS fails to validate CSRF tokens, allowing attackers to bypass protection and perform unauthorized actions on behalf of users.","url":"https://insights.sbomify.com/CVE-2017-16570/"}