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.
- 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
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
Which versions are affected by CVE-2017-16570?
2 open source packages ship an affected version, including keystone. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
keystone npm | All versions | 4.0.0-beta.7 |
keystone npm | All versions | 4.0.0-beta.7 |
Products include 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: 1 Exploit-DB entry.
Other vulnerabilities in n/a
- CVE-2022-39382 NODE_ENV in Keystone defaults to development with esbuild
- CVE-2022-29354 File upload in n/a
- CVE-2022-39322 @keystone-6/core vulnerable to field-level access-control bypass for multiselect field
- CVE-2017-15879 Keystone is vulnerable to CSV injection
- CVE-2015-9240 Authentication Weakness in keystone
Sources
Also known as GHSA-q43c-g2g7-6gxj.