CVE-2020-5275GHSA-G4M9-5HPF-HX72BIT-SYMFONY-2020-5275
Firewall configured with unanimous strategy was not actually unanimous in symfony/security-http
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.4.7, 5.0.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- symfony symfony
From 4.4.0 · fixed in 4.4.7; From 5.0.0 · fixed in 5.0.7
- symfony/securityPackagist
From 4.4.0 · fixed in 4.4.7
- symfony/securityPackagist
From 5.0.0 · fixed in 5.0.7
- symfony/security-httpPackagist
From 4.4.0 · fixed in 4.4.7
- symfony/security-httpPackagist
From 5.0.0 · fixed in 5.0.7
- symfony/symfonyPackagist
From 4.4.0 · fixed in 4.4.7
- symfony/symfonyPackagist
From 5.0.0 · fixed in 5.0.7