# CVE-2020-5275: Firewall configured with unanimous strategy was not actually unanimous in Symfony

Source: https://junglewise.ai/threats/cve-2020-5275-firewall-configured-with-unanimous-strategy-was-not-actually  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2020-03-30  
License: CC BY 4.0 with a link back

CVE-2020-5275 · Severity: low · CVSS 3.1 · Published 2020-03-30

Firewall configured with unanimous strategy was not actually unanimous in Symfony

Technologies: [symfony/security (Packagist)](https://junglewise.ai/threats/technologies/symfony-security), [symfony/security-http (Packagist)](https://junglewise.ai/threats/technologies/symfony-security-http), [symfony/symfony (Packagist)](https://junglewise.ai/threats/technologies/symfony-symfony). Vendors: [Packagist](https://junglewise.ai/threats/vendors/packagist).

## Quick answers

**Is CVE-2020-5275 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2020-5275 being exploited in the wild.

**How severe is CVE-2020-5275?** Low severity, with a CVSS score of 3.1, published 30 March 2020.

**Which products and versions are affected?** symfony/security (Packagist) ECOSYSTEM:introduced=4.4.0,fixed=4.4.7; symfony/security-http (Packagist) ECOSYSTEM:introduced=4.4.0,fixed=4.4.7; symfony/symfony (Packagist) ECOSYSTEM:introduced=4.4.0,fixed=4.4.7.

**Is there a fix for CVE-2020-5275?** Yes. symfony/security (Packagist): upgrade to 4.4.7 or later; symfony/security-http (Packagist): upgrade to 4.4.7 or later; symfony/symfony (Packagist): upgrade to 4.4.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2020-5275?** Check whether you run symfony/security (Packagist), symfony/security-http (Packagist) or symfony/symfony (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- symfony/security (Packagist): upgrade to 4.4.7 or later

  ```sh
  composer require symfony/security:^4.4.7
  ```

- symfony/security-http (Packagist): upgrade to 4.4.7 or later

  ```sh
  composer require symfony/security-http:^4.4.7
  ```

- symfony/symfony (Packagist): upgrade to 4.4.7 or later

  ```sh
  composer require symfony/symfony:^4.4.7
  ```


## Affected products

- symfony/security (Packagist) ECOSYSTEM:introduced=4.4.0,fixed=4.4.7
- symfony/security-http (Packagist) ECOSYSTEM:introduced=4.4.0,fixed=4.4.7
- symfony/symfony (Packagist) ECOSYSTEM:introduced=4.4.0,fixed=4.4.7

## Identifiers

- CVE-2020-5275
- GHSA-g4m9-5hpf-hx72

## Related threats

- [Symfony YAML stack exhaustion in inline lexer](https://junglewise.ai/threats/cve-2026-109413-in-symfony-yaml-prior-to-versions-5-4-54-6-4-45-7-4-18-and-8-1-6)
- [Symfony HTTP Foundation ReDoS in HeaderUtils::split()](https://junglewise.ai/threats/cve-2026-108082-symfony-is-a-php-framework-for-web-and-console-applications-and)
- [Symfony Routing improper dot-segment encoding in UrlGenerator](https://junglewise.ai/threats/cve-2026-48784-symfony-routing-improper-dot-segment-encoding-in-urlgenerator)
- [Symfony HtmlSanitizer XSS via incomplete URL attribute sanitization](https://junglewise.ai/threats/cve-2026-48761-symfony-htmlsanitizer-xss-via-incomplete-url-attribute)
- [Symfony HtmlSanitizer visual spoofing via percent-encoded BiDi characters](https://junglewise.ai/threats/cve-2026-48760-symfony-htmlsanitizer-visual-spoofing-via-percent-encoded-bidi)