GHSA-q8j7-fjh7-25v5 Symfony collectionCascaded and collectionCascadedDeeply fields security bypass

• Packagist symfony/validator: >= 2.0.0, < 2.0.24 → fixed in 2.0.24 • Packagist symfony/validator: >= 2.1.0, < 2.1.12 → fixed in 2.1.12 • Packagist symfony/validator: >= 2.2.0, < 2.2.5 → fixed in 2.2.5 • Packagist symfony/validator: >= 2.3.0, < 2.3.3 → fixed in 2.3.3 • Packagist symfony/symfony: >= 2.0.0, < 2.0.24 → fixed in 2.0.24 • Packagist symfony/symfony: >= 2.1.0, < 2.1.12 → fixed in 2.1.12 • Packagist symfony/symfony: >= 2.2.0, < 2.2.5 → fixed in 2.2.5 • Packagist symfony/symfony: >= 2.3.0, < 2.3.3 → fixed in 2.3.3

When using the Validator component, if `Symfony\\Component\\Validator\\Mapping\\Cache\\ApcCache` is enabled (or any other cache implementing `Symfony\\Component\\Validator\\Mapping\\Cache\\CacheInterface`), some information is lost during serialization (the `collectionCascaded` and the `collectionCascadedDeeply` fields). As a consequence, arrays or traversable objects stored in fields using the `@Valid` constraint are not traversed by the validator as soon as the validator configuration is loaded from the cache.