@neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields
What fixes it
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
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.
Text from CVE List
Affected versions 2
- @neo4j/graphqlaffected: 3.23.0 before 7.6.4CVE List
- @neo4j/graphql, npm<= 7.6.3GitHub
References 4
- github.com/neo4j/graphql/commit/ef69cc69ff5e97c60d64aa524005f939c5ba3633Fixvia CVE List
- github.com/neo4j/graphql/releases/tag/%40neo4j%2Fgraphql%407.6.4Fixvia CVE List
- github.com/neo4j/graphql/security/advisories/GHSA-8xj4-8gg9-fx9hAdvisoryvia CVE List
- npmjs.com/package/@neo4j/graphqlReferencevia CVE List