Symfony Security-Http vulnerabilities
15 known vulnerabilities affecting symfony/security-http.
Total CVEs
15
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
HIGH7MEDIUM7LOW1
Vulnerabilities
Page 1 of 1
CVE-2024-36611MEDIUM≥ 0, < 7.1.02024-11-29
CVE-2024-36611 [MEDIUM] CWE-287 Withdrawn Advisory: Symfony http-security has authentication bypass
Withdrawn Advisory: Symfony http-security has authentication bypass
## Withdrawn Advisory
This advisory has been withdrawn because the report is not part of a valid vulnerability. This link is maintained to preserve external references. For more information, see advisory-database/pull/5046.
## Original Description
In Symfony, a security vulnerability was identified in the FormLoginAuthenticator
ghsa
CVE-2024-51996HIGH≥ 5.3.0, < 5.4.47≥ 6.0.0-BETA1, < 6.4.15+1 more2024-11-13
CVE-2024-51996 [HIGH] CWE-287 Symfony has an Authentication Bypass via RememberMe
Symfony has an Authentication Bypass via RememberMe
### Description
When consuming a persisted remember-me cookie, Symfony does not check if the username persisted in the database matches the username attached with the cookie, leading to authentication bypass.
### Resolution
The `PersistentRememberMeHandler` class now ensures the submitted username is the cookie owner.
The patch for this issue is available [he
ghsaosv
CVE-2023-46733MEDIUM≥ 5.4.21, < 5.4.31≥ 6.2.7, < 6.3.82023-11-12
CVE-2023-46733 [MEDIUM] CWE-384 Symfony possible session fixation vulnerability
Symfony possible session fixation vulnerability
### Description
SessionStrategyListener does not always migrate the session after a successful login. It only migrate the session when the logged-in user identifier changes. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fu
ghsaosv
CVE-2015-8125HIGH≥ 2.4.0, < 2.6.12≥ 2.7.0, < 2.7.72022-05-17
CVE-2015-8125 [HIGH] CWE-208 Symfony Vulnerable to Timing Attack
Symfony Vulnerable to Timing Attack
Symfony 2.3.x before 2.3.35, 2.6.x before 2.6.12, and 2.7.x before 2.7.7 might allow remote attackers to have unspecified impact via a timing attack involving the (1) `Symfony/Component/Security/Http/RememberMe/PersistentTokenBasedRememberMeServices` or (2) `Symfony/Component/Security/Http/Firewall/DigestAuthenticationListener` class in the Symfony Security Component, or (3) legacy CSRF implemen
ghsaosv
CVE-2016-4423HIGH≥ 2.3.0, < 2.3.41≥ 2.4.0, < 2.7.13+2 more2022-05-17
CVE-2016-4423 [HIGH] Symphony Denial of Service Via Overlong Usernames
Symphony Denial of Service Via Overlong Usernames
The attemptAuthentication function in `Component/Security/Http/Firewall/UsernamePasswordFormAuthenticationListener.php` in Symfony before 2.3.41, 2.7.x before 2.7.13, 2.8.x before 2.8.6, and 3.0.x before 3.0.6 does not limit the length of a username stored in a session, which allows remote attackers to cause a denial of service (session storage consumption) via a series of au
ghsaosv
CVE-2018-11385HIGH≥ 2.7.0, < 2.7.48≥ 2.8.0, < 2.8.41+3 more2022-05-14
CVE-2018-11385 [HIGH] CWE-384 Symfony Session Fixation Vulnerability
Symfony Session Fixation Vulnerability
An issue was discovered in the Security component in Symfony 2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, and 4.0.x before 4.0.11. A session fixation vulnerability within the "Guard" login feature may allow an attacker to impersonate a victim towards the web application if the session id value was previously known to the attacker.
ghsaosv
CVE-2018-11406HIGH≥ 2.7.0, < 2.7.48≥ 2.8.0, < 2.8.41+3 more2022-05-14
CVE-2018-11406 [HIGH] CWE-352 Symfony CSRF Token Fixation
Symfony CSRF Token Fixation
An issue was discovered in the Security component in Symfony 2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, and 4.0.x before 4.0.11. By default, a user's session is invalidated when the user is logged out. This behavior can be disabled through the invalidate_session option. In this case, CSRF tokens were not erased during logout which allowed for CSRF token fixation.
ghsaosv
CVE-2017-16652MEDIUM≥ 2.7.0, < 2.7.38≥ 2.8.0, < 2.8.31+2 more2022-05-14
CVE-2017-16652 [MEDIUM] CWE-601 Symfony Open Redirect
Symfony Open Redirect
An issue was discovered in Symfony 2.7.x before 2.7.38, 2.8.x before 2.8.31, 3.2.x before 3.2.14, and 3.3.x before 3.3.13. `DefaultAuthenticationSuccessHandler` or `DefaultAuthenticationFailureHandler` takes the content of the `_target_path` parameter and generates a redirect response, but no check is performed on the path, which could be an absolute URL to an external domain. This Open redirect vulnerability can be exp
ghsaosv
CVE-2018-19790MEDIUM≥ 2.7.38, < 2.7.50≥ 2.8.0, < 2.8.49+4 more2022-05-14
CVE-2018-19790 [MEDIUM] CWE-601 Symfony Open Redirect
Symfony Open Redirect
An open redirect was discovered in Symfony 2.7.x before 2.7.50, 2.8.x before 2.8.49, 3.x before 3.4.20, 4.0.x before 4.0.15, 4.1.x before 4.1.9 and 4.2.x before 4.2.1. By using backslashes in the `_failure_path` input field of login forms, an attacker can work around the redirection target restrictions and effectively redirect the user to any domain after login.
ghsaosv
CVE-2015-8124LOW≥ 2.4.0, < 2.6.12≥ 2.7.0, < 2.7.72022-05-14
CVE-2015-8124 [LOW] CWE-384 Symfony Session Fixation Vulnerability
Symfony Session Fixation Vulnerability
A session fixation vulnerability within the "Remember Me" login feature allows an attacker to impersonate the victim towards the web application if the session id value was previously known to the attacker. This issue has been fixed in Symfony 2.3.35, 2.6.12, and 2.7.7. Note that no fixes are provided for Symfony 2.4 and 2.5 as they are not maintained anymore. Symfony 2.8 and 3.0 haven't be
ghsaosv
CVE-2021-32693MEDIUM≥ 5.3.0, < 5.3.22021-06-21
CVE-2021-32693 [MEDIUM] CWE-287 Authentication granted to all firewalls instead of just one
Authentication granted to all firewalls instead of just one
Description
When an application defines multiple firewalls, the authenticated token delivered by one of the firewalls is available to all other firewalls. This can be abused when the application defines different providers for different parts of an application. In such a situation, a user authenticated on one part of the application is consider
ghsaosv
CVE-2021-21424MEDIUM≥ 5.1.0, < 5.2.82021-05-13
CVE-2021-21424 [MEDIUM] CWE-200 Prevent user enumeration using Guard or the new Authenticator-based Security
Prevent user enumeration using Guard or the new Authenticator-based Security
Description
The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticati
ghsaosv
CVE-2020-5275HIGH≥ 4.4.0, < 4.4.7≥ 5.0.0, < 5.0.72020-03-30
CVE-2020-5275 [HIGH] CWE-285 Firewall configured with unanimous strategy was not actually unanimous in Symfony
Firewall configured with unanimous strategy was not actually unanimous in Symfony
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 th
ghsaosv
CVE-2019-10911HIGH≥ 2.7.0, < 2.7.51≥ 2.8.0, < 2.8.50+3 more2020-02-12
CVE-2019-10911 [HIGH] CWE-200 Improper authentication in Symfony
Improper authentication in Symfony
In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, a vulnerability would allow an attacker to authenticate as a privileged user on sites with user registration and remember me login functionality enabled. This is related to symfony/security.
ghsaosv
CVE-2019-18886MEDIUM≥ 4.1.0, < 4.2.12≥ 4.3.0, < 4.3.82019-12-02
CVE-2019-18886 [MEDIUM] CWE-200 User enumeration leak using switch user functionality in Symfony
User enumeration leak using switch user functionality in Symfony
An issue was discovered in Symfony 4.2.0 to 4.2.11 and 4.3.0 to 4.3.7. The ability to enumerate users was possible due to different handling depending on whether the user existed when making unauthorized attempts to use the switch users functionality. This is related to symfony/security.
ghsaosv