# CVE-2021-32624: Private Field data leak

> Attackers can bypass access controls to reveal private field values in Keystone 5 CMS, exposing sensitive data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-27g8-r9vw-765x

## What is CVE-2021-32624?

CVE-2021-32624 is a high-severity vulnerability in keystonejs keystone-5, published on 24 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2021-32624?

2 open source packages ship an affected version, including @keystonejs/keystone. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@keystonejs/keystone` | npm | All versions to 19.3.2 | None |
| `@keystonejs/keystone` | npm | All versions to 19.3.2 | None |

Products: Keystonejs Keystone-5.

## How do I fix CVE-2021-32624?

No fix has been published for CVE-2021-32624 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-32624 being exploited?

There is no known exploitation of CVE-2021-32624 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32624 and fix it if it is affected.

What it is: CVE-2021-32624 is a high-severity vulnerability in keystonejs keystone-5, published on 24 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-32624 in the wild and no public exploit code.

Affected packages and fixed versions:
- @keystonejs/keystone (npm): affected all versions up to 19.3.2; no fix listed
- @keystonejs/keystone (npm): affected all versions up to 19.3.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-32624/ (Markdown: https://insights.sbomify.com/CVE-2021-32624/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-32624
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-32624
- OSV: https://osv.dev/vulnerability/CVE-2021-32624

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-32624/
Summaries are generated and may contain mistakes; the official description above is the record.