CSRF in Keystonejs Keystone
CVE-2017-16570
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.
Vulnerability class: CSRF (Cross-Site Request Forgery)
EPSS: 0.002 (41.8th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
Affected products
- Keystonejs Keystone
- N/a — versions n/a
Weakness classification (CWE)
Public proof-of-concept exploits
References
- cve@mitre.org (Third Party Advisory, x_refsource_MISC, Issue Tracking)
- cve@mitre.org (Third Party Advisory, x_refsource_MISC, Issue Tracking)
- cve@mitre.org (Third Party Advisory, x_refsource_MISC, Issue Tracking)
- cve@mitre.org (exploit, x_refsource_EXPLOIT-DB)
Frequently asked questions
- What is CVE-2017-16570?
- CVE-2017-16570 is a high-severity vulnerability in Keystonejs Keystone, classified under Cross-Site Request Forgery (CSRF). CVSS score: 8.8/10. Published 2017-11-06.
- How severe is CVE-2017-16570?
- High severity. CVSS v3 base score is 8.8 out of 10.
- Is CVE-2017-16570 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.