KeystoneJS up to 4.0.0-beta.6 CSRF Prevention cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in KeystoneJS up to 4.0.0-beta.6. The affected element is an unknown function of the component CSRF Prevention. The manipulation results in cross-site request forgery. This vulnerability is known as CVE-2017-16570. It is possible to launch the attack remotely. Furthermore, an exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic has been found in KeystoneJS up to 4.0.0-beta.6. Affected is an unknown code block of the component CSRF Prevention. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. CVE summarizes:
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.
The bug was discovered 11/06/2017. The weakness was published 11/06/2017 (Website). The advisory is available at blog.securelayer7.net. This vulnerability is traded as CVE-2017-16570 since 11/06/2017. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. Technical details are unknown but a public exploit is available.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 4.0.0-beta.7 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (43922). Similar entry is available at VDB-108617. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: KeystoneJS 4.0.0-beta.7
Patch: github.com
Timeline
11/06/2017 🔍11/06/2017 🔍
11/06/2017 🔍
11/06/2017 🔍
11/07/2017 🔍
07/29/2025 🔍
Sources
Advisory: 4437Status: Confirmed
CVE: CVE-2017-16570 (🔍)
GCVE (CVE): GCVE-0-2017-16570
GCVE (VulDB): GCVE-100-109170
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 11/07/2017 08:05Updated: 07/29/2025 01:51
Changes: 11/07/2017 08:05 (58), 12/04/2019 18:04 (5), 01/06/2023 14:36 (5), 07/29/2025 01:51 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.