@neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Neo4j | @neo4j/graphql | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Neo4j | Graphql |
|
Vendor Solution
Upgrade @neo4j/graphql to version 7.6.4 or later.
Vendor Workaround
Apply @authentication directly to each top-level @cypher field. Where possible, run the GraphQL service account with least-privilege database permissions.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.370% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Neo4j
Neo4j graphql |
|
| Vendors & Products |
Neo4j
Neo4j graphql |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | @neo4j/graphql: schema-level and type-level @authentication not enforced on top-level @cypher fields | |
| Weaknesses | CWE-306 | |
| References |
| |
| Metrics |
cvssV4_0
|