CVE-2017-16570: CSRF

Published Nov 6, 2017
·
Updated

KeystoneJS before 4.0.0-beta.7 allows application-wide CSRF bypass by removing the CSRF parameter and value, aka SecureLayer7 issue number SL7KEYJS03. In other words, it fails to reject requests that lack an x-csrf-token header.

Affected Software

1 affected component
Keystonejs Keystone<4.0.0

Event History

Nov 6, 2017
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-16570?

CVE-2017-16570 is classified as a medium severity vulnerability due to its potential to allow CSRF attacks.

2

How do I fix CVE-2017-16570?

To fix CVE-2017-16570, upgrade KeystoneJS to version 4.0.0-beta.7 or later.

3

What type of vulnerability is CVE-2017-16570?

CVE-2017-16570 is a Cross-Site Request Forgery (CSRF) vulnerability that compromises request validation.

4

Which versions of KeystoneJS are affected by CVE-2017-16570?

CVE-2017-16570 affects all versions of KeystoneJS prior to 4.0.0-beta.7.

5

What is the consequence of CVE-2017-16570?

Exploitation of CVE-2017-16570 can lead to unauthorized actions performed on behalf of an authenticated user.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203