LowGHSA-j5jh-hpr4-h332CVE-2015-8124

Symfony Session Fixation Vulnerability

Published 14 May 2022 · Updated 16 Feb 2024

Affected packages

symfony/symfonyComposer

Affected: >=2.3.0 <2.3.35
Fixed in: 2.3.35

Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.3.35

symfony/symfonyComposer

Affected: >=2.4.0 <2.6.12
Fixed in: 2.6.12

Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.6.12

symfony/symfonyComposer

Affected: >=2.7.0 <2.7.7
Fixed in: 2.7.7

Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.7.7

symfony/security-httpComposer

Affected: >=2.4.0 <2.6.12
Fixed in: 2.6.12

Update to the fixed version for your release line, for example:composer require symfony/security-http:^2.6.12

symfony/security-httpComposer

Affected: >=2.7.0 <2.7.7
Fixed in: 2.7.7

Update to the fixed version for your release line, for example:composer require symfony/security-http:^2.7.7

symfony/securityComposer

Affected: >=2.3.0 <2.3.35
Fixed in: 2.3.35

Update to the fixed version for your release line, for example:composer require symfony/security:^2.3.35

symfony/securityComposer

Affected: >=2.4.0 <2.6.12
Fixed in: 2.6.12

Update to the fixed version for your release line, for example:composer require symfony/security:^2.6.12

symfony/securityComposer

Affected: >=2.7.0 <2.7.7
Fixed in: 2.7.7

Update to the fixed version for your release line, for example:composer require symfony/security:^2.7.7

Details

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.

Is GHSA-j5jh-hpr4-h332 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected symfony/symfony, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.