GraphQL grant on a property might be cached with different objects
api-platform core
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| api-platform/graphql Packagist |
|
|
| api-platform/core Packagist |
api-platform core
| Product | Affected | Fixed in |
|---|---|---|
| api-platform/graphql Packagist |
|
|
| api-platform/core Packagist |
≥ 4.0.0-alpha.1 · < 4.0.22< 3.4.17≥ 4.1.0-alpha.1 · < 4.1.5
|
API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Prior to 4.0.22 and 3.4.17, a GraphQL grant on a property might be cached with different objects. The ApiPlatform\GraphQl\Serializer\ItemNormalizer::isCacheKeySafe() method is meant to prevent the caching but the parent::normalize method that is called afterwards still creates the cache key and causes the issue. This vulnerability is fixed in 4.0.22 and 3.4.17.
From the CVE record · GitHub_M
A GraphQL property grant may be cached and reused for a different object because normalization still creates a cache key. This can cause a grant intended for one object to be applied to another. The input does not specify authentication requirements or user interaction.
Teams using the Packagist packages api-platform/core or api-platform/graphql should check versions before 3.4.17, from 4.0.0-alpha.1 to before 4.0.22, or from 4.1.0-alpha.1 to before 4.1.5.