HighGHSA-wfv7-5x33-v22hCVE-2014-4931

Code injection in the way Symfony implements translation caching in FrameworkBundle

Published 30 May 2024 · Updated 30 May 2024

Affected packages

symfony/framework-bundleComposer
Affected
>=2.0.0 <2.3.18
Fixed in
2.3.18
Update to the fixed version for your release line, for example:composer require symfony/framework-bundle:^2.3.18
symfony/framework-bundleComposer
Affected
>=2.4.0 <2.4.8
Fixed in
2.4.8
Update to the fixed version for your release line, for example:composer require symfony/framework-bundle:^2.4.8
symfony/framework-bundleComposer
Affected
>=2.5.0 <2.5.2
Fixed in
2.5.2
Update to the fixed version for your release line, for example:composer require symfony/framework-bundle:^2.5.2
symfony/symfonyComposer
Affected
>=2.0.0 <2.3.19
Fixed in
2.3.19
Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.3.19
symfony/symfonyComposer
Affected
>=2.4.0 <2.4.9
Fixed in
2.4.9
Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.4.9
symfony/symfonyComposer
Affected
>=2.5.0 <2.5.4
Fixed in
2.5.4
Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.5.4

Details

When investigating issue #11093, Jeremy Derussé found a serious code injection issue in the way Symfony implements translation caching in FrameworkBundle.

  • Your Symfony application is vulnerable if you meet the following conditions:
  • You are using the Symfony translation system from FrameworkBundle (so basically if you are using Symfony full-stack -- you are not affected if you are using the Translation component with Silex for instance);

You don't sanitize locales coming from a URL (any route with a _locale argument for instance):

When vulnerable, an attacker can submit a non-valid locale value that can contain some PHP code that will be executed by Symfony. That's because the locale value is dumped into a PHP file generated in the cache without being sanitized first.

Is GHSA-wfv7-5x33-v22h 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/framework-bundle, and gives you the command that fixes it.

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

References

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