Firewall configured with unanimous strategy was not actually unanimous in symfony/security-http
symfony
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/security Packagist |
|
|
| symfony/security-http Packagist |
|
symfony
| Product | Affected | Fixed in |
|---|---|---|
| symfony/security Packagist |
|
|
| symfony/security-http Packagist |
|
|
| symfony/symfony Packagist |
|
|
In symfony/security-http before versions 4.4.7 and 5.0.7, when a `Firewall` checks access control rule, it iterate overs each rule's attributes and stops as soon as the accessDecisionManager decides to grant access on the attribute, preventing the check of next attributes that should have been take into account in an unanimous strategy. The accessDecisionManager is now called with all attributes at once, allowing the unanimous strategy being applied on each attribute. This issue is patched in versions 4.4.7 and 5.0.7.
From the CVE record · GitHub_M
Symfony's Firewall can grant access after checking only one attribute of an access control rule, instead of evaluating all attributes under the unanimous strategy. This can allow access that the rule should deny when it has multiple attributes; the input does not specify authentication or user-interaction requirements.
Teams running Packagist packages symfony/security, symfony/security-http, or symfony/symfony in versions >=4.4.0 <4.4.7 or >=5.0.0 <5.0.7 should check their installations.