Skip to content

Symfony Session Fixation Vulnerability

Low severity GitHub Reviewed Published May 14, 2022 to the GitHub Advisory Database • Updated Feb 8, 2024

Package

composer symfony/security (Composer)

Affected versions

>= 2.3.0, < 2.3.35
>= 2.4.0, < 2.6.12
>= 2.7.0, < 2.7.7

Patched versions

2.3.35
2.6.12
2.7.7
composer symfony/security-http (Composer)
>= 2.4.0, < 2.6.12
>= 2.7.0, < 2.7.7
2.6.12
2.7.7
composer symfony/symfony (Composer)
>= 2.3.0, < 2.3.35
>= 2.4.0, < 2.6.12
>= 2.7.0, < 2.7.7
2.3.35
2.6.12
2.7.7

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.

References

Published by the National Vulnerability Database Dec 7, 2015
Published to the GitHub Advisory Database May 14, 2022
Reviewed Aug 2, 2023
Last updated Feb 8, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

EPSS score

1.537%
(88th percentile)

Weaknesses

CVE ID

CVE-2015-8124

GHSA ID

GHSA-j5jh-hpr4-h332

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.