Skip to content

Private Field data leak

High severity GitHub Reviewed Published May 24, 2021 in keystonejs/keystone-5 • Updated Feb 1, 2023

Package

npm @keystonejs/keystone (npm)

Affected versions

<= 19.3.2

Patched versions

None

Description

This security advisory relates to a newly discovered capability in our query infrastructure to directly or indirectly expose the values of private fields, bypassing the configured access control.

This is an access control related oracle attack in that the attack method guides an attacker during their attempt to reveal information they do not have access to. The complexity of completing the attack is limited by some length-dependent behaviors and the fidelity of the exposed information.

Impact

Under some circumstances, field values or field value meta data can be determined, despite the field or list having read access control configured. If you use private fields or lists, you may be impacted.

Patches

None, at this time

Workarounds

None, at this time

References

None

For more information

For the protection of the community and private deployments, we think that the best course of action will be to not disclose further details on any open GitHub issues related to this advisory until a hot-fix or work-around has been deployed or published.

If needed, you can email us at keystone@thinkmill.com.au

References

@molomby molomby published to keystonejs/keystone-5 May 24, 2021
Published by the National Vulnerability Database May 24, 2021
Reviewed May 25, 2021
Published to the GitHub Advisory Database May 27, 2021
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.063%
(29th percentile)

Weaknesses

CVE ID

CVE-2021-32624

GHSA ID

GHSA-27g8-r9vw-765x

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.