Keystone 5
Approved changes feed: RSS · Atom
cpe:2.3:a:keystonejs:keystone-5:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Keystonejs (21fb8261-6b57-5151-9316-12b3e439d143) |
|---|---|
| Product | Keystone 5 (b4fbb9cb-50b3-5171-91bc-7a4b191daf0e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/keystonejs/keystone-5 |
purl2cpe | 2026-06-01 10:14:37.947061 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-32624 |
vulnerable | 2026-06-08 05:32:07.688530 |
Private Field data leak
HIGH (7.5)
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
Published: 2021-05-24T16:55:09.000Z
Updated: 2024-08-03T23:25:31.007Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.