Skip to content

Symfony collectionCascaded and collectionCascadedDeeply fields security bypass

High severity GitHub Reviewed Published May 5, 2022 to the GitHub Advisory Database • Updated Feb 7, 2024

Package

composer symfony/symfony (Composer)

Affected versions

>= 2.0.0, < 2.0.24
>= 2.1.0, < 2.1.12
>= 2.2.0, < 2.2.5
>= 2.3.0, < 2.3.3

Patched versions

2.0.24
2.1.12
2.2.5
2.3.3
composer symfony/validator (Composer)
>= 2.0.0, < 2.0.24
>= 2.1.0, < 2.1.12
>= 2.2.0, < 2.2.5
>= 2.3.0, < 2.3.3
2.0.24
2.1.12
2.2.5
2.3.3

Description

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.

References

Published by the National Vulnerability Database Nov 1, 2019
Published to the GitHub Advisory Database May 5, 2022
Reviewed Aug 17, 2023
Last updated Feb 7, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.210%
(60th percentile)

Weaknesses

CVE ID

CVE-2013-4751

GHSA ID

GHSA-q8j7-fjh7-25v5

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.