Neo4j @neo4j/graphql
@neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields
In @neo4j/graphql versions up to and including 7.6.3, @authentication directives applied at the schema level or on the Query or Mutation types are silently ignored for top-level fields annotated with @cypher. Only @authentication directives placed directly on the individual fields are enforced. An application that exposes a top-level @cypher field and relies on schema-level or type-level @authentication to protect it allows unauthenticated callers to invoke the field and run the configured Cypher statement with the privileges of the GraphQL service account, which may permit reading and modifying data. Fixed in 7.6.4.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.23.0, < 7.6.4
Fixed in 7.6.4
Mitigation
Upgrade @neo4j/graphql to version 7.6.4 or later.
Workaround
Apply @authentication directly to each top-level @cypher field. Where possible, run the GraphQL service account with least-privilege database permissions.
References
- Vendor advisory github.com/neo4j/graphql/security/advisories/G…
- Patch github.com/neo4j/graphql/commit/ef69cc69ff5e97…
- Release notes github.com/neo4j/graphql/releases/tag/%40neo4j…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.