~ / search / GHSA-g4m9-5hpf-hx72

GHSA-g4m9-5hpf-hx72

Firewall configured with unanimous strategy was not actually unanimous in Symfony

Source: GitHub Advisory Database (reviewed) High CVE-2020-5275

Packages

EcosystemPackageAffectedFixed in
Packagist symfony/security >= 4.4.0, < 4.4.7 4.4.7
Packagist symfony/security >= 5.0.0, < 5.0.7 5.0.7
Packagist symfony/security-http >= 4.4.0, < 4.4.7 4.4.7
Packagist symfony/security-http >= 5.0.0, < 5.0.7 5.0.7
Packagist symfony/symfony >= 4.4.0, < 4.4.7 4.4.7
Packagist symfony/symfony >= 5.0.0, < 5.0.7 5.0.7

Details

As written in the advisory (Markdown source, shown as plain text).

Description ----------- On Symfony before 4.4.0, when a `Firewall` checks an access control rule (using the unanimous strategy), it iterates over all rule attributes and grant access only if *all* calls to the `accessDecisionManager` decide to grant access. As of Symfony 4.4.0, a bug was introduced that prevents the check of attributes as soon as `accessDecisionManager` decide to grant access on one attribute. Resolution ---------- The `accessDecisionManager` is now called with all attributes at once, allowing the unanimous strategy being applied on each attribute. The patch for this issue is available [here](https://github.com/symfony/symfony/commit/c935e4a3fba6cc2ab463a6ca382858068d63cebf) for the 4.4 branch. Credits ------- I would like to thank Antonio J. García Lagar for reporting & Robin Chalas for fixing the issue.

References

External links from the advisory. They lead to third-party sites.