CVE-2017-16570
UnknownEPSS 2.21%
Last modified
CVE-2017-16570 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.21% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Keystonejs | Keystone | < 4.0.0 | Beta7 |
References
- http://blog.securelayer7.net/keystonejs-open-source-penetration-testing-report/Issue Tracking, Third Party Advisory
- https://github.com/keystonejs/keystone/issues/4437Issue Tracking, Third Party Advisory
- https://github.com/keystonejs/keystone/pull/4478Issue Tracking, Third Party Advisory
- http://blog.securelayer7.net/keystonejs-open-source-penetration-testing-report/Issue Tracking, Third Party Advisory
- https://github.com/keystonejs/keystone/issues/4437Issue Tracking, Third Party Advisory
- https://github.com/keystonejs/keystone/pull/4478Issue Tracking, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is 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.
How severe is CVE-2017-16570?
Severity scoring for CVE-2017-16570 is pending analysis. The EPSS model estimates a 2.21% probability of exploitation in the next 30 days.
How do I fix CVE-2017-16570?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-16564Stored Cross-site scripting (XSS) vulnerability in /cgi-bin/…
- CVE-2017-16565Cross-Site Request Forgery (CSRF) in /cgi-bin/login on Vonag…
- CVE-2017-16566On Jooan IP Camera A5 2.3.36 devices, an insecure FTP server…9.8
- CVE-2017-16567Persistent Cross-Site Scripting (XSS) vulnerability in Logit…5.4
- CVE-2017-16568Persistent Cross-Site Scripting (XSS) vulnerability in Logit…5.4
- CVE-2017-16569An Open URL Redirect issue exists in Zurmo 3.2.1.57987acc301…
- CVE-2017-16571This vulnerability allows remote attackers to execute arbitr…
- CVE-2017-16572This vulnerability allows remote attackers to execute arbitr…
- CVE-2017-16573This vulnerability allows remote attackers to disclose sensi…
- CVE-2017-16574This vulnerability allows remote attackers to disclose sensi…
- CVE-2017-16575This vulnerability allows remote attackers to execute arbitr…
- CVE-2017-16576This vulnerability allows remote attackers to execute arbitr…
Are you affected by CVE-2017-16570?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST