Spring GraphQL Annotation Detection Vulnerability
Spring for GraphQL
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.graphql:spring-graphql Maven |
|
|
Spring for GraphQL
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.graphql:spring-graphql Maven |
|
|
The Spring GraphQL annotation detection mechanism for @Controller data fetchers may not correctly resolve annotations on methods within type hierarchies. This can be an issue if such annotations are used for authorization decisions. When all conditions are met, security annotations can be ignored at runtime.
Affected versions: Spring for GraphQL 2.0.0 through 2.0.3; 1.4.0 through 1.4.5; 1.3.0 through 1.3.8; 1.0.0 through 1.0.6.
From the CVE record · vmware
Spring for GraphQL may fail to resolve annotations on @Controller data-fetcher methods within type hierarchies. If those annotations are used for authorization decisions and all triggering conditions are met, they can be ignored at runtime, potentially bypassing authorization checks. The input does not specify network or local access requirements, authentication requirements, or user interaction.
Teams running Spring for GraphQL 2.0.0–2.0.3, 1.4.0–1.4.5, 1.3.0–1.3.8, or 1.0.0–1.0.6 should check their deployments.