CVE-2017-16570
N/A
Published: November 6, 2017 at 08:00 AM UTC
Updated: June 17, 2026 at 01:09 AM UTC
1 product affected across 1 vendorKeystone
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 2%
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.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
95%
v < 4.0.0beta7
Affected range stops below 4.0.0, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.
References (4)
x_refsource_MISCIssue TrackingThird Party Advisory
Source: [email protected]
http://blog.securelayer7.net/keystonejs-open-source-penetration-testing-report/x_refsource_MISCIssue TrackingThird Party Advisory
Source: [email protected]
https://github.com/keystonejs/keystone/issues/4437x_refsource_MISCIssue TrackingThird Party Advisory
Source: [email protected]
https://github.com/keystonejs/keystone/pull/4478Quick Info
StatusMODIFIED
CWE
CWE-352
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card