Page 3 of 12 results (0.002 seconds)

CVSS: 8.8EPSS: 0%CPEs: 5EXPL: 0

Symfony is a PHP framework for web and console applications and a set of reusable PHP components. When authenticating users Symfony by default regenerates the session ID upon login, but preserves the rest of session attributes. Because this does not clear CSRF tokens upon login, this might enables same-site attackers to bypass the CSRF protection mechanism by performing an attack similar to a session-fixation. This issue has been fixed in the 4.4 branch. • https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-bundle/CVE-2022-24895.yaml https://github.com/symfony/security-bundle/commit/076fd2088ada33d760758d98ff07ddedbf567946 https://github.com/symfony/symfony/commit/5909d74ecee359ea4982fcf4331aaf2e489a1fd4 https://github.com/symfony/symfony/security/advisories/GHSA-3gv2-29qc-v67m https://lists.debian.org/debian-lts-announce/2023/07/msg00014.html • CWE-384: Session Fixation CWE-613: Insufficient Session Expiration •

CVSS: 8.8EPSS: 0%CPEs: 3EXPL: 0

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. • https://github.com/symfony/symfony/commit/f0ffb775febdf07e57117aabadac96fa37857f50 https://github.com/symfony/symfony/security/advisories/GHSA-vvmr-8829-6whx • CWE-352: Cross-Site Request Forgery (CSRF) •