Quick answers
- Is CVE-2022-39322 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-39322 being exploited in the wild.
- How severe is CVE-2022-39322?
- Low severity, with a CVSS score of 3.1, published 18 October 2022.
- Which products and versions are affected?
- @keystone-6/core (npm) SEMVER:introduced=2.2.0,fixed=2.3.1.
- Is there a fix for CVE-2022-39322?
- Yes. @keystone-6/core (npm): upgrade to 2.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-39322 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2022-39322?
- Check whether you run @keystone-6/core (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @keystone-6/core (npm): upgrade to 2.3.1 or later
npm install @keystone-6/core@2.3.1
Technical details
A field-level access-control bypass exists in the multiselect field implementation of Keystone 6 versions 2.2.0 and 2.3.0. The vulnerability allows attackers on the network to bypass access control rules defined at the field level (create and update permissions) without requiring authentication or user interaction. The flaw affects only multiselect fields with field-level access control; list-level access control and other field types are not impacted. An attacker can read confidential data and modify protected field values. The issue is fixed in version 2.3.1 and later.
Affected products
- Keystone @keystone-6/core 2.2.0 through 2.3.0
Identifiers
- CVE-2022-39322
- GHSA-6mhr-52mv-6v6f
Timeline
- 2022-10-18: disclosed: Advisory published
- 2022-10-18: patched: Fix released in version 2.3.1