GHSA-j5jh-hpr4-h332 CVE-2015-8124
Symfony Session Fixation Vulnerability
- Severity
- 3.1 / 10
- Low · CVSS 3.1
- Exploit chance (EPSS)
- 2.71%
- Chance of exploitation in the next 30 days. Higher than 85.99% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-384 Session Fixation
- Fix
- Available
- 3 packages have a fixed version
Description
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 been released yet and the fix will be included in their first stable releases.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| symfony/security | >= 2.3.0, < 2.3.35 |
2.3.35 |
| symfony/security | >= 2.4.0, < 2.6.12 |
2.6.12 |
| symfony/security | >= 2.7.0, < 2.7.7 |
2.7.7 |
| symfony/security-http | >= 2.4.0, < 2.6.12 |
2.6.12 |
| symfony/security-http | >= 2.7.0, < 2.7.7 |
2.7.7 |
| symfony/symfony | >= 2.3.0, < 2.3.35 |
2.3.35 |
| symfony/symfony | >= 2.4.0, < 2.6.12 |
2.6.12 |
| symfony/symfony | >= 2.7.0, < 2.7.7 |
2.7.7 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
symfony/security Packagist → 2.3.35
- composer
composer require symfony/security:^2.3.35
symfony/security-http Packagist → 2.6.12
- composer
composer require symfony/security-http:^2.6.12
symfony/symfony Packagist → 2.3.35
- composer
composer require symfony/symfony:^2.3.35
Severity breakdown
CVSS 3.1 3.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-384: Session Fixation
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
How to prevent it
- Architecture and Design: Invalidate any existing session identifiers prior to authorizing a new user session.
- Architecture and Design: For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value. If the session variable and the cookie value ever don't match, invalidate the session, and force the user to log on again.
- Operation: Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
References
Advisories
Other links
- github.com/symfony/symfony/pull/16631
- github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-http/C…
- github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security/CVE-20…
- github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-201…
- symfony.com/blog/cve-2015-8124-session-fixation-in-the-remember-me-login-feature
- symfony.com/cve-2015-8124
- web.archive.org/web/20201209020014/http://www.securityfocus.com/archive/1/537183/100…
- web.archive.org/web/20210125123853/http://www.securityfocus.com/bid/77694
- lists.fedoraproject.org/pipermail/package-announce/2015-December/173271.html
- lists.fedoraproject.org/pipermail/package-announce/2015-December/173300.html
- seclists.org/fulldisclosure/2015/Dec/89
- debian.org/security/2015/dsa-3402
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-2v3c-qxhr-7vpv Symfony: Unbounded Recursion in the YAML Inline Lexer Lets a Single Document Crash the Process | High | Also affects symfony/symfony |
| GHSA-r925-mgvr-h9cc Symfony: ReDoS in HeaderUtils::split() Reachable Through the Cache-Control Request Header | High | Also affects symfony/symfony |
| GHSA-h5x3-xfc9-m39h Symfony: UrlGenerator Dot-Segment Encoding Skips Every Other Chained `../` or `./` → Generated URL Collapses Off-Route Under RFC 3986 Normalization | Medium | Also affects symfony/symfony |
| GHSA-v3wm-qf9p-c549 Symfony: HtmlSanitizer URL Parser Deny Gates Underinclusive: Percent-Encoded BiDi Marks and Unicode Whitespace Bypass Visual-Spoofing Defense | Medium | Also affects symfony/symfony |
| GHSA-rrj9-5q2j-4gvr Symfony: Mailomat Mailer Webhook Parser Reads the HMAC Algorithm from the Request: Signature Algorithm Downgrade | Medium | Also affects symfony/symfony |
| GHSA-38cx-cq6f-5755 Symfony: IpUtils::PRIVATE_SUBNETS Omits IPv6 Transition Forms (6to4, NAT64, Teredo, IPv4-compatible): SSRF Bypass in NoPrivateNetworkHttpClient | High | Also affects symfony/symfony |
| GHSA-6h46-9jf5-q59x Symfony: Security Firewall Bypass via failure_forward Subrequest: Unauthenticated Access to access_control-Protected GET Routes | High | Also affects symfony/security-http |
| GHSA-x5qj-865h-mgvm Symfony: HtmlSanitizer UrlAttributeSanitizer Misses URL Attributes | Medium | Also affects symfony/symfony |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor