All reports
High

Firewall configured with unanimous strategy was not actually unanimous in Symfony

Affected versions

Version ranges need review.

Affected versions
>= 4.4.0, < 4.4.7
Fixed version
4.4.7
Affected versions
>=4.4.0,<4.4.7|>=5.0.0,<5.0.7
Fixed version
Not reported
Affected versions
>= 5.0.0, < 5.0.7
Fixed version
5.0.7
Affected versions
>= 4.4.0, < 4.4.7
Fixed version
4.4.7
Affected versions
>= 5.0.0, < 5.0.7
Fixed version
5.0.7
Affected versions
>= 5.0.0, < 5.0.7
Fixed version
5.0.7
Affected versions
>=4.4.0,<4.4.7|>=5.0.0,<5.0.7
Fixed version
Not reported
Affected versions
>= 4.4.0, < 4.4.7
Fixed version
4.4.7

Exploitation

CVE-2020-5275

Probability of exploitation in the next 30 days: 1.15%

FIRST EPSS · 2026-11-20

Description

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 for the 4.4 branch.

Credits

I would like to thank Antonio J. García Lagar for reporting & Robin Chalas for fixing the issue.

Links

Credits

  • ajgarlag
  • chalasr