Quick answers
- Is CVE-2021-32624 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2021-32624 being exploited in the wild.
- How severe is CVE-2021-32624?
- Low severity, with a CVSS score of 3.1, published 27 May 2021.
- Which products and versions are affected?
- KeystoneJS Keystone 5 <= 19.3.2; @keystonejs/keystone (npm) SEMVER:introduced=0,last_affected=19.3.2.
- Is there a fix for CVE-2021-32624?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2021-32624 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2021-32624?
- Check whether you run KeystoneJS Keystone 5 or @keystonejs/keystone (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.
Technical details
Keystone 5 is vulnerable to an access control oracle attack within its query infrastructure (CWE-200). The flaw allows an authenticated attacker with low privileges to directly or indirectly determine the values of private fields or metadata, even when 'read' access controls are explicitly configured. The attack complexity is considered high as it relies on observing length-dependent behaviors and the fidelity of exposed information to reconstruct sensitive data. At the time of disclosure, no official patches or workarounds were available for the affected versions (up to 19.3.2).
Affected products
- KeystoneJS Keystone 5 (@keystonejs/keystone) <= 19.3.2
Identifiers
- CVE-2021-32624
- GHSA-27g8-r9vw-765x
Timeline
- 2021-05-24: advisory: Initial advisory published by KeystoneJS and NVD
- 2021-05-27: disclosed: GHSA published