CVE-2020-5275: Firewall configured with unanimous strategy was not actually unanimous in symfony/security-http

Published Mar 30, 2020
·
Updated

CVE-2020-5275: All rules set in "accesscontrol" are required when the firewall is configured with the unanimous strategy

Other sources

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.

GitHub

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.

Affected Software

11 affected componentsFixes available
composer/symfony/security-http>=4.4.0, <4.4.7, >=5.0.0, <5.0.7
composer/symfony/security>=4.4.0, <4.4.7
composer/symfony/symfony>=4.4.0, <4.4.7, >=5.0.0, <5.0.7
composer/symfony/symfony>=5.0.0<5.0.7
5.0.7
composer/symfony/symfony>=4.4.0<4.4.7
4.4.7
composer/symfony/security-http>=5.0.0<5.0.7
5.0.7
composer/symfony/security-http>=4.4.0<4.4.7
4.4.7
composer/symfony/security>=5.0.0<5.0.7
5.0.7
composer/symfony/security>=4.4.0<4.4.7
4.4.7
SensioLabs Symfony>=4.4.0<4.4.7
SensioLabs Symfony>=5.0.0<5.0.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 5.0.7
  2. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 4.4.7
  3. Upgrade

    Upgrade composer/symfony/security-http to a version that resolves this vulnerability.

    Fixed in 5.0.7
  4. Upgrade

    Upgrade composer/symfony/security-http to a version that resolves this vulnerability.

    Fixed in 4.4.7
  5. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 5.0.7
  6. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 4.4.7
  7. Upgrade

    Upgrade Symfony (symfony/security-http) to a version that resolves this vulnerability.

    Fixed in 4.4.7
  8. Upgrade

    Upgrade Symfony (symfony/security-http) to a version that resolves this vulnerability.

    Fixed in 5.0.7

Event History

Mar 30, 2020
Advisory Published
02:00 PM
CVE Published
via MITRE·07:45 PM
Data Sourced
via MITRE·07:45 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is CVE-2020-5275?

CVE-2020-5275 is a vulnerability in the symfony/security-http package before versions 4.4.7 and 5.0.7.

2

How does CVE-2020-5275 impact the firewall configuration?

CVE-2020-5275 affects the firewall configuration in Symfony, where it stops checking access control rules as soon as access is granted on an attribute, potentially allowing unauthorized access.

3

What is the severity level of CVE-2020-5275?

CVE-2020-5275 has a high severity level with a CVSS score of 8.1.

4

How can I fix CVE-2020-5275?

To fix CVE-2020-5275, you should update the affected symfony/security-http package to version 4.4.7 or 5.0.7.

5

Where can I find more information about CVE-2020-5275?

You can find more information about CVE-2020-5275 on the Symfony website and the relevant GitHub commits and advisories.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203