CVE-2017-16570
Cross-Site Request Forgery (CSRF) in keystone
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
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.
- Record
CVE-2017-16570- CVSS 3.0
- 8.8 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - CVSS 2.0
- 6.8 Medium
AV:N/AC:M/Au:N/C:P/I:P/A:P - Weakness
- CWE-352
- Updated
- 2026-11-02
CVE List No score
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.
- Record
CVE-2017-16570- Updated
- 2026-11-02
EUVDEUVD-2017-0351 No score
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.
- Record
EUVD-2017-0351- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-q43c-g2g7-6gxj
Cross-Site Request Forgery (CSRF) in keystone
Versions of keystone prior to 4.0.0 are vulnerable to Cross-Site Request Forgery (CSRF). The package fails to validate the presence of the X-CSRF-Token header, which may allow attackers to carry actions on behalf of other users on all endpoints.
Recommendation
Update to version 4.0.0 or later.
- Record
GHSA-q43c-g2g7-6gxj- CVSS 3.0
- 8.8 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-352
- Updated
- 2026-11-02
OSV
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.
- Record
CVE-2017-16570- CVSS 3.0
- 8.8 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVGHSA-q43c-g2g7-6gxj
Cross-Site Request Forgery (CSRF) in keystone
Versions of keystone prior to 4.0.0 are vulnerable to Cross-Site Request Forgery (CSRF). The package fails to validate the presence of the X-CSRF-Token header, which may allow attackers to carry actions on behalf of other users on all endpoints.
Recommendation
Update to version 4.0.0 or later.
- Record
GHSA-q43c-g2g7-6gxj- CVSS 3.0
- 8.8 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-352
- Updated
- 2026-11-02
Affected products
Affected packages
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| Exploit-DB | KeystoneJS < 4.0.0-beta.7 - Cross-Site Request Forgery | 2018-01-28 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, Exploit-DB, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2017-16570 is a high vulnerability (CVSS 8.8) in Keystonejs Keystone, published November 6, 2017. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 2.21%, the 82nd percentile. Fixed in keystone 4.0.0-beta.7.
References
blog.securelayer7.net/keystonejs-open-source-penetration-testing-report
github.com/keystonejs/keystone/issues/4437
exploit-db.com/exploits/43922
nvd.nist.gov/vuln/detail/CVE-2017-16570
securelayer7.net/download/pdf/KeystoneJS-Pentest-Report-SecureLayer7.pdf
snyk.io/vuln/SNYK-JS-KEYSTONE-449663
npmjs.com/advisories/979