LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32624: Private Field data leak

Keystone 5 is an open source CMS platform to build Node.js applications. 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. 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. No patches exist at this time. There are no workarounds at this time

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-32624 can let an authenticated user infer or expose Keystone 5 private field data despite configured read restrictions. The advisory says systems using private fields or private lists may be impacted. The source bundle states no patch or workaround was available in the cited advisory.

Executive priority

Handle as a high-priority exposure review if Keystone 5 protects sensitive private fields. Business urgency depends on whether affected applications are internet-facing, allow broad authentication, or store regulated data.

Technical view

Keystone 5 query infrastructure contains an access-control oracle issue that can directly or indirectly reveal private field values or metadata. It bypasses configured field or list read access controls. Affected product is keystonejs keystone-5 versions <= 19.3.2. CVSS is 7.5 high with network attack vector and low privileges required.

Likely exposure

Exposure is likely limited to organizations running Keystone 5 <= 19.3.2, especially applications using private fields or private lists for sensitive data. The issue requires low-privileged access, so public self-registration or many authenticated users increase concern.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The advisory describes a high-complexity oracle attack with length-dependent behavior and imperfect fidelity, but it can still reveal private data under some circumstances.

Researcher notes

Do not assume full plaintext disclosure in every case. The advisory describes direct or indirect exposure with limits from length-dependent behavior and information fidelity. Evidence is incomplete on real-world exploitation and fixed versions in the supplied sources.

Mitigation direction

  • Inventory Keystone 5 applications and confirm whether versions are <= 19.3.2.
  • Identify private fields and private lists containing sensitive business or personal data.
  • Check the Keystone advisory and vendor channels for current guidance before changing controls.
  • Reduce low-trust authenticated access to affected applications where operationally feasible.
  • Treat sensitive private-field data as potentially exposed until vendor guidance confirms otherwise.

Validation and detection

  • Confirm Keystone 5 package versions in deployed applications and build artifacts.
  • Review application schema for private fields, private lists, and read access control assumptions.
  • Map who can authenticate to affected Keystone applications, including self-service accounts.
  • Review logs for unusual authenticated querying against sensitive lists or fields.
  • Track the CVE record and GitHub advisory for patch or workaround updates.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32624 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-32624Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
keystonejskeystone-5<= 19.3.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.