Symfony collectionCascaded and collectionCascadedDeeply fields security bypass
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2013-4751US | high8.1 | — | ||
php-symfony2-Validator has loss of information during serialization | ||||
references
External citations — patches, advisories, analysis.
- http://lists.fedoraproject.org/pipermail/package-announce/2013-August/114380.htmlWEB
- http://lists.fedoraproject.org/pipermail/package-announce/2013-August/114436.htmlWEB
- http://symfony.com/blog/security-releases-symfony-2-0-24-2-1-12-2-2-5-and-2-3-3-releasedWEB
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-4751WEB
- https://exchange.xforce.ibmcloud.com/vulnerabilities/86364WEB
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2013-4751.yamlWEB
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/validator/CVE-2013-4751.yamlWEB
- https://github.com/symfony/validatorPACKAGE
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan