Search for packages
Package details: pkg:composer/symfony/validator@2.3.3
purl pkg:composer/symfony/validator@2.3.3
Next non-vulnerable version 5.4.43
Latest non-vulnerable version 7.1.4
Risk 1.4
Vulnerabilities affecting this package (1)
Vulnerability Summary Fixed by
VCID-fhmx-pjm9-zqdd
Aliases:
CVE-2024-50343
GHSA-g3rh-rrhp-jhh9
Symfony has an incorrect response from Validator when input ends with `\n` ### Description It is possible to trick a `Validator` configured with a regular expression using the `$` metacharacters, with an input ending with `\n`. ### Resolution Symfony now uses the `D` regex modifier to match the entire input. The patch for this issue is available [here](https://github.com/symfony/symfony/commit/7d1032bbead9a4229b32fa6ebca32681c80cb76f) for branch 5.4. ### Credits We would like to thank Offscript for reporting the issue and Alexandre Daubois for providing the fix.
5.4.43
Affected by 0 other vulnerabilities.
6.4.11
Affected by 0 other vulnerabilities.
7.1.4
Affected by 0 other vulnerabilities.
Vulnerabilities fixed by this package (1)
Vulnerability Summary Aliases
VCID-mrwn-pp7p-ffa9 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. CVE-2013-4751
GHSA-q8j7-fjh7-25v5