# CVE-2017-16570: Cross-Site Request Forgery (CSRF) in keystone

> KeystoneJS fails to validate CSRF tokens, allowing attackers to bypass protection and perform unauthorized actions on behalf of users.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q43c-g2g7-6gxj

## What is CVE-2017-16570?

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.

### Official 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2017-16570?

2 open source packages ship an affected version, including keystone. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `keystone` | npm | All versions | 4.0.0-beta.7 |
| `keystone` | npm | All versions | 4.0.0-beta.7 |

Products: Keystonejs Keystone.

## How do I fix CVE-2017-16570?

Upgrade keystone to 4.0.0-beta.7 or later.

## Is CVE-2017-16570 being exploited?

There is no known exploitation of CVE-2017-16570 in the wild and no public exploit code.

Public exploit code:

- KeystoneJS < 4.0.0-beta.7 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2022-39382](https://insights.sbomify.com/CVE-2022-39382/): NODE_ENV in Keystone defaults to development with esbuild (critical 9.8)
- [CVE-2022-29354](https://insights.sbomify.com/CVE-2022-29354/): File upload in n/a (critical 9.8)
- [CVE-2022-39322](https://insights.sbomify.com/CVE-2022-39322/): @keystone-6/core vulnerable to field-level access-control bypass for multiselect field (critical 9.1)
- [CVE-2017-15879](https://insights.sbomify.com/CVE-2017-15879/): Keystone is vulnerable to CSV injection (high 8.8)
- [CVE-2015-9240](https://insights.sbomify.com/CVE-2015-9240/): Authentication Weakness in keystone (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16570 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2017-16570 in the wild and no public exploit code.

Affected packages and fixed versions:
- keystone (npm): affected all versions; fixed in 4.0.0-beta.7
- keystone (npm): affected all versions; fixed in 4.0.0-beta.7

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-16570/ (Markdown: https://insights.sbomify.com/CVE-2017-16570/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-16570
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-16570
- OSV: https://osv.dev/vulnerability/CVE-2017-16570

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-16570/
Summaries are generated and may contain mistakes; the official description above is the record.