Cross-Site Request Forgery (CSRF) in keystone
Versions of `keystone` prior to 4.0.0 are vulnerable to Cross-Site Request Forgery (CSRF). The package fails to validate the presence of the `X-CSRF-Token` header, which may allow attackers to carry actions on behalf of other users on all endpoints. ## Recommendation Update to version 4.0.0 or later.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2017-16570US | high8.8 | Exploit | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- http://blog.securelayer7.net/keystonejs-open-source-penetration-testing-reportWEB
- https://github.com/advisories/GHSA-q43c-g2g7-6gxjADVISORY
- https://github.com/keystonejs/keystone/issues/4437WEB
- https://github.com/keystonejs/keystone/pull/4478WEB
- https://nvd.nist.gov/vuln/detail/CVE-2017-16570ADVISORY
- https://securelayer7.net/download/pdf/KeystoneJS-Pentest-Report-SecureLayer7.pdfWEB
- https://snyk.io/vuln/SNYK-JS-KEYSTONE-449663WEB
- https://www.exploit-db.com/exploits/43922WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan