CVE-2017-16570

Public Exploit

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.

Category

8.8
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.21%
Third-Party Advisory securelayer7.net Third-Party Advisory github.com Third-Party Advisory github.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
http://blog.securelayer7.net/keystonejs-open-source-penetration-testing-report/ issue tracking third party advisory
https://github.com/keystonejs/keystone/issues/4437 issue tracking third party advisory
https://github.com/keystonejs/keystone/pull/4478 issue tracking third party advisory
https://www.exploit-db.com/exploits/43922/ exploit

Frequently Asked Questions

What is the severity of CVE-2017-16570?
CVE-2017-16570 has been scored as a high severity vulnerability.
How to fix CVE-2017-16570?
To fix CVE-2017-16570, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-16570 being actively exploited in the wild?
It is possible that CVE-2017-16570 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.