Keystone
Keystone: `graphql.maxTake` bypass with negative `take`
Keystone is a content management system for Node.js. Prior to 6.5.3, the findMany resolver in packages/core/src/lib/core/queries/resolvers.ts compares the signed take argument directly with graphql.maxTake, allowing a remote unauthenticated GraphQL client to provide a negative take value whose magnitude exceeds the configured bound. The bypass also applies to relationship queries and can return more records than the developer intended, potentially exhausting service resources. This issue is fixed in version 6.5.3.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.5high · scored by CNA · CWE-20
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
keystonejs keystone
- < 6.5.3
Fixed in 6.5.3
Mitigation
Upgrade keystone to 6.5.3 or later.
References
- Vendor advisory github.com/keystonejs/keystone/security/adviso…
- Patch github.com/keystonejs/keystone/pull/9859
- Patch github.com/keystonejs/keystone/commit/9fb88b24…
1 more
- Release notes github.com/keystonejs/keystone/releases/tag/@k…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.