Vulnerability in Keystonejs Keystone
CVE-2022-39382
Keystone is a headless CMS for Node.js — built with GraphQL and React.`@keystone-6/core@3.0.0 || 3.0.1` users that use `NODE_ENV` to trigger security-sensitive functionality in their production builds are vulnerable to `NODE_ENV` being inlined to `"development"` for user code, irrespective of what your environment variables. If you do not use `NODE_ENV` in your user code to trigger security-sensitive functionality, you are not impacted by this vulnerability. Any dependencies that use `NODE_ENV` to trigger particular behaviors (optimizations, security or otherwise) should still respect your environment's configured `NODE_ENV` variable. The application's dependencies, as found in `node_modules` (including `@keystone-6/core`), are typically not compiled as part of this process, and thus should be unaffected. We have tested this assumption by verifying that `NODE_ENV=production yarn keystone start` still uses secure cookies when using `statelessSessions`. This vulnerability has been fixed in @keystone-6/core@3.0.2, regression tests have been added for this vulnerability in #8063.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.021, 81.6th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Keystonejs Keystone — versions >= 3.0.0, < 3.0.2, 3.0.1, 3.0.0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (20142995/nuclei-templates, cyb3r-w0lf/nuclei-template-collection). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/keystonejs/keystone/security/advisories/GHSA-25mx-2mxm-6343 (Exploit, Third Party Advisory)
- github.com/keystonejs/keystone/pull/8031/ (Patch, Third Party Advisory)
- github.com/keystonejs/keystone/pull/8063 (Patch, Third Party Advisory)