GHSA-5fp6-4xw3-xqq3: @keystone 6/core @keystone-6/core's Bundled Cuid Package Known Vulnerability

LOW
Share
Published
Advisory Summary

GHSA-5fp6-4xw3-xqq3 is a LOW @keystone-6/core's bundled cuid package known vulnerability (General Security Weakness) affecting @keystone 6/core libraries in the npm ecosystem. The issue involves @keystone-6/core's bundled cuid package known to be insecure. Remediation is available in the latest vendor maintenance releases.

GHSA-5fp6-4xw3-xqq3 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-5fp6-4xw3-xqq3
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product @keystone 6/core
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-5fp6-4xw3-xqq3

To remediate this vulnerability, upgrade all affected @keystone 6/core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@keystone-6/core fixed: Latest secure release 
npm install @keystone-6/core@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @keystone-6/core

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-5fp6-4xw3-xqq3, inspect your project dependencies using npm:

npm ls @keystone-6/core

Analyze the terminal output to locate any version of @keystone 6/core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls @keystone-6/core command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In @keystone 6/core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary The `cuid` package used by `@keystone-6/*` and upstream dependencies is deprecated and [marked as insecure by the author](https://github.com/paralleldrive/cuid#status-deprecated-due-to-security-use-cuid2-instead). As reported by the author > Cuid and other k-sortable and non-cryptographic ids (Ulid, ObjectId, KSUID, all UUIDs) are all insecure. Use @paralleldrive/cuid2 instead. ### What are doing about this? - [We are waiting on Prisma](https://github.com/keystonejs/keystone/issues/8282) to add support for [`cuid2`](https://github.com/paralleldrive/cuid2) - Alternatively, we might default to a random string ourselves ### What can I do about this? We have added a work-around for users who want to provide custom identifiers in https://github.com/keystonejs/keystone/pull/8645 ### What if I need a `cuid`? The features marked as a security vulnerability by @paralleldrive are sometimes actually needed ([as written in the README of `cuid`](https://github.com/paralleldrive/cuid#motivation)) - the problem is the inherent risks that features like this can have. You might actually want the features of a monotonically increasing (auto-increment, k-sortable), and timestamp-based id as part of your application, and keystone should support that - but you might not want them by _default_. This is why this security advisory has been accepted by me (@dcousens), we currently use cuid identifiers by default, and that should change. ### Impact I have accepted this security advisory on the basis that we don't need this kind of identifier typically, and the need for them should be driven by an application's requirements, not a convenient default.

GHSA-5fp6-4xw3-xqq3 Affected @keystone 6/core Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
@keystone-6/core
npm/@keystone-6/core
npm
≤ 5.3.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/keystonejs/keystone/security/advisories/GHSA-5fp6-4xw3-xqq3
@keystone 6/core Source Repository REPOSITORY
https://github.com/keystonejs/keystone/issues/8282#issuecomment-1586019823
@keystone 6/core Source Repository REPOSITORY
https://github.com/keystonejs/keystone
@keystone 6/core Source Repository REPOSITORY
https://github.com/paralleldrive/cuid#status-deprecated-due-to-security-use-cuid2-instead

Frequently Asked Questions

What is GHSA-5fp6-4xw3-xqq3?
GHSA-5fp6-4xw3-xqq3 is a security vulnerability in @keystone 6/core involving @keystone-6/core's bundled cuid package known to be insecure under General Security Weakness.
Which @keystone 6/core versions are affected?
Affected versions include releases prior to current release patches across affected packages: @keystone-6/core.
What version fixes GHSA-5fp6-4xw3-xqq3?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is @keystone-6/core affected?
Yes, @keystone-6/core is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-5fp6-4xw3-xqq3?
GHSA-5fp6-4xw3-xqq3 is classified under General Security Weakness.
How can I check npm dependencies for GHSA-5fp6-4xw3-xqq3?
Run the dependency tree command: 'npm ls @keystone-6/core'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5fp6-4xw3-xqq3",
  "modified" : "2023-06-23T13:56:28Z",
  "published" : "2023-06-12T18:37:31Z",
  "aliases" : [ ],
  "summary" : "@keystone-6/core's bundled cuid package known to be insecure",
  "details" : "### Summary\nThe `cuid` package used by `@keystone-6/*` and upstream dependencies is deprecated and [marked as insecure by the author](https://github.com/paralleldrive/cuid#status-deprecated-due-to-security-use-cuid2-instead).\n\nAs reported by the author\n> Cuid and other k-sortable and non-cryptographic ids (Ulid, ObjectId, KSUID, all UUIDs) are all insecure. Use @paralleldrive/cuid2 instead.\n\n### What are doing about this?\n- [We are waiting on Prisma](https://github.com/keystonejs/keystone/issues/8282) to add support for [`cuid2`](https://github.com/paralleldrive/cuid2)\n- Alternatively, we might default to a random string ourselves\n\n### What can I do about this?\nWe have added a work-around for users who want to provide custom identifiers in https://github.com/keystonejs/keystone/pull/8645\n\n### What if I need a `cuid`?\nThe features marked as a security vulnerability by @paralleldrive are sometimes actually needed ([as written in the README of `cuid`](https://github.com/paralleldrive/cuid#motivation)) - the problem is the inherent risks that features like this can have.\n\nYou might actually want the features of a monotonically increasing (auto-increment, k-sortable), and timestamp-based id as part of your application, and keystone should support that - but you might not want them by _default_.\nThis is why this security advisory has been accepted by me (@dcousens), we currently use cuid identifiers by default, and that should change.\n\n### Impact\nI have accepted this security advisory on the basis that we don't need this kind of identifier typically, and the need for them should be driven by an application's requirements, not a convenient default.\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@keystone-6/core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "5.3.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/keystonejs/keystone/security/advisories/GHSA-5fp6-4xw3-xqq3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/keystonejs/keystone/issues/8282#issuecomment-1586019823"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/keystonejs/keystone"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/paralleldrive/cuid#status-deprecated-due-to-security-use-cuid2-instead"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-06-12T18:37:31Z",
    "nvd_published_at" : null
  }
}