VulnerabilityModified
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.
HIGH 8.8EPSS 2.21%
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (2.21%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a 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.
- CVSS 3.0
- 8.8 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS
- 2.21% probability · 82th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-352
- Affected
- keystonejs/keystone
- Source
- cve@mitre.org
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
- https://www.exploit-db.com/exploits/43922/
- 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
- https://www.exploit-db.com/exploits/43922/
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.