FKIE_CVE-2022-39382

Vulnerability from fkie_nvd - Published: 2022-11-03 14:15 - Updated: 2024-11-21 07:18
Severity ?
9.8 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
9.8 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
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.
References
security-advisories@github.comhttps://github.com/keystonejs/keystone/pull/8031/Patch, Third Party Advisory
security-advisories@github.comhttps://github.com/keystonejs/keystone/pull/8063Patch, Third Party Advisory
security-advisories@github.comhttps://github.com/keystonejs/keystone/security/advisories/GHSA-25mx-2mxm-6343Exploit, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/keystonejs/keystone/pull/8031/Patch, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/keystonejs/keystone/pull/8063Patch, Third Party Advisory
af854a3a-2127-422b-91ae-364da2661108https://github.com/keystonejs/keystone/security/advisories/GHSA-25mx-2mxm-6343Exploit, Third Party Advisory
Impacted products
Vendor Product Version
keystonejs keystone 3.0.0
keystonejs keystone 3.0.1
To clipboard 

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:keystonejs:keystone:3.0.0:*:*:*:*:node.js:*:*",
              "matchCriteriaId": "2A1639F4-A82C-44BD-906A-EBC32CAFA194",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:keystonejs:keystone:3.0.1:*:*:*:*:node.js:*:*",
              "matchCriteriaId": "509439A0-C352-4697-B8F7-190F583386FA",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Keystone is a headless CMS for Node.js \u2014 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\u0027s configured `NODE_ENV` variable. The application\u0027s 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."
    },
    {
      "lang": "es",
      "value": "Keystone es un CMS headless para Node.js construido con GraphQL y React.`@keystone-6/core@3.0.0 || 3.0.1` los usuarios que usan `NODE_ENV` para activar funciones sensibles a la seguridad en sus compilaciones de producci\u00f3n son vulnerables a que `NODE_ENV` se incluya en `\"desarrollo\"` para el c\u00f3digo de usuario, independientemente de cu\u00e1les sean sus variables de entorno. Si no utiliza `NODE_ENV` en su c\u00f3digo de usuario para activar funciones sensibles a la seguridad, esta vulnerabilidad no lo afecta. Cualquier dependencia que use `NODE_ENV` para desencadenar comportamientos particulares (optimizaciones, seguridad o de otro tipo) a\u00fan debe respetar la variable `NODE_ENV` configurada en su entorno. Las dependencias de la aplicaci\u00f3n, como se encuentran en `node_modules` (incluido `@keystone-6/core`), normalmente no se compilan como parte de este proceso y, por lo tanto, no deber\u00edan verse afectadas. Hemos probado esta suposici\u00f3n verificando que `NODE_ENV = inicio clave del hilo de producci\u00f3n` todav\u00eda usa cookies seguras cuando se usan `statelessSessions`. Esta vulnerabilidad se solucion\u00f3 en @keystone-6/core@3.0.2, se agregaron pruebas de regresi\u00f3n para esta vulnerabilidad en el n\u00famero 8063."
    }
  ],
  "id": "CVE-2022-39382",
  "lastModified": "2024-11-21T07:18:10.783",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 9.8,
          "baseSeverity": "CRITICAL",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 5.9,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      },
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 9.8,
          "baseSeverity": "CRITICAL",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 5.9,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ]
  },
  "published": "2022-11-03T14:15:23.767",
  "references": [
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Patch",
        "Third Party Advisory"
      ],
      "url": "https://github.com/keystonejs/keystone/pull/8031/"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Patch",
        "Third Party Advisory"
      ],
      "url": "https://github.com/keystonejs/keystone/pull/8063"
    },
    {
      "source": "security-advisories@github.com",
      "tags": [
        "Exploit",
        "Third Party Advisory"
      ],
      "url": "https://github.com/keystonejs/keystone/security/advisories/GHSA-25mx-2mxm-6343"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Patch",
        "Third Party Advisory"
      ],
      "url": "https://github.com/keystonejs/keystone/pull/8031/"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Patch",
        "Third Party Advisory"
      ],
      "url": "https://github.com/keystonejs/keystone/pull/8063"
    },
    {
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Exploit",
        "Third Party Advisory"
      ],
      "url": "https://github.com/keystonejs/keystone/security/advisories/GHSA-25mx-2mxm-6343"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Modified",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-74"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    },
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-74"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.