Advisory

GHSA-6mhr-52mv-6v6f

Also known as: CVE-2022-39322

Summary

Field-level access-control bypass for multiselect field

Details

Impact

@keystone-6/[email protected] || 2.3.0 users who are using the multiselect field, and provided field-level access control - are vulnerable to their field-level access control not being used.

List-level access control is NOT affected.

Field-level access control for fields other than multiselect are NOT affected.

Example, you are vulnerable if you are using field-level access control on a multiselect like the following:

const yourList = list({
  access: {
    // this is list-level access control, this is NOT impacted
  },
  fields: {
    yourFieldName: multiselect({
      // this is field-level access control, for multiselect fields
      //   this is vulnerable
      access: {
        create: ({ session }) => session?.data.isAdmin,
        update: ({ session }) => session?.data.isAdmin,
      },
      options: [
        { value: 'apples', label: 'Apples' },
        { value: 'oranges', label: 'Oranges' },
      ],
      // ...
    }),
    // ...
  },
  // ...
});

Mitigation
Please upgrade to @keystone-6/core >= 2.3.1, where this vulnerability has been closed.

Workarounds
If for some reason you cannot upgrade your dependencies, you should stop using the multiselect field.

Credits
Thanks to Marek R for reporting and submitting the pull request to fix this problem.

If you have any questions around this security advisory, please don't hesitate to contact us at [[email protected]](mailto:[email protected]), or open an issue on GitHub.

If you have a security flaw to report for any software in this repository, please see our SECURITY policy.

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2022-10-18 17:12 UTC
Modified
2023-11-08 04:10 UTC

Affected packages and fixes

@keystone-6/core

npm · All systems

Affected

  • introduced 2.2.0, fixed 2.3.1 (semver)

Fixed versions

2.3.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences