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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2017-0351 | 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. |
Github GHSA |
GHSA-q43c-g2g7-6gxj | Cross-Site Request Forgery (CSRF) in keystone |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-05T20:27:03.997Z
Reserved: 2017-11-06T00:00:00
Link: CVE-2017-16570
No data.
Status : Deferred
Published: 2017-11-06T08:29:00.377
Modified: 2025-04-20T01:37:25.860
Link: CVE-2017-16570
No data.
OpenCVE Enrichment
No data.
EUVD
Github GHSA