Symfony is a PHP framework for web and console applications and a set of reusable PHP components. The Symfony form component provides a CSRF protection mechanism by using a random token injected in the form and using the session to store and control the token submitted by the user. When using the FrameworkBundle, this protection can be enabled or disabled with the configuration. If the configuration is not specified, by default, the mechanism is enabled as long as the session is enabled. In a recent change in the way the configuration is loaded, the default behavior has been dropped and, as a result, the CSRF protection is not enabled in form when not explicitly enabled, which makes the application sensible to CSRF attacks. This issue has been resolved in the patch versions listed and users are advised to update. There are no known workarounds for this issue. Reference: https://github.com/symfony/symfony/security/advisories/GHSA-vvmr-8829-6whx Upstream patch: https://github.com/symfony/symfony/commit/f0ffb775febdf07e57117aabadac96fa37857f50
Created php-symfony tracking bugs for this issue: Affects: epel-7 [bug 2049794] Affects: fedora-all [bug 2049795]
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.