CriticalGHSA-pgwj-prpq-jpc2CVE-2019-10910

Symfony Service IDs Allow Injection

Published 18 Nov 2019 · Updated 29 May 2025

Is your project on an affected symfony/dependency-injection?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2.7.0 <2.7.51
Fixed in
2.7.51
Update to the fixed version for your release line, for example:composer require symfony/dependency-injection:^2.7.51
Affected
>=2.8.0 <2.8.50
Fixed in
2.8.50
Update to the fixed version for your release line, for example:composer require symfony/dependency-injection:^2.8.50
Affected
>=3.0.0 <3.4.26
Fixed in
3.4.26
Update to the fixed version for your release line, for example:composer require symfony/dependency-injection:^3.4.26
Affected
>=4.0.0 <4.1.12
Fixed in
4.1.12
Update to the fixed version for your release line, for example:composer require symfony/dependency-injection:^4.1.12
Affected
>=4.2.0 <4.2.7
Fixed in
4.2.7
Update to the fixed version for your release line, for example:composer require symfony/dependency-injection:^4.2.7
Affected
>=2.7.0 <2.7.51
Fixed in
2.7.51
Update to the fixed version for your release line, for example:composer require symfony/proxy-manager-bridge:^2.7.51
Affected
>=2.8.0 <2.8.50
Fixed in
2.8.50
Update to the fixed version for your release line, for example:composer require symfony/proxy-manager-bridge:^2.8.50
Affected
>=3.0.0 <3.4.26
Fixed in
3.4.26
Update to the fixed version for your release line, for example:composer require symfony/proxy-manager-bridge:^3.4.26
Affected
>=4.0.0 <4.1.12
Fixed in
4.1.12
Update to the fixed version for your release line, for example:composer require symfony/proxy-manager-bridge:^4.1.12
Affected
>=4.2.0 <4.2.7
Fixed in
4.2.7
Update to the fixed version for your release line, for example:composer require symfony/proxy-manager-bridge:^4.2.7
Affected
>=2.7.0 <2.7.51
Fixed in
2.7.51
Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.7.51
Affected
>=2.8.0 <2.8.50
Fixed in
2.8.50
Update to the fixed version for your release line, for example:composer require symfony/symfony:^2.8.50
Affected
>=3.0.0 <3.4.26
Fixed in
3.4.26
Update to the fixed version for your release line, for example:composer require symfony/symfony:^3.4.26
Affected
>=4.0.0 <4.1.12
Fixed in
4.1.12
Update to the fixed version for your release line, for example:composer require symfony/symfony:^4.1.12
Affected
>=4.2.0 <4.2.7
Fixed in
4.2.7
Update to the fixed version for your release line, for example:composer require symfony/symfony:^4.2.7

Details

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, when service ids allow user input, this could allow for SQL Injection and remote code execution. This is related to symfony/dependency-injection.

Is GHSA-pgwj-prpq-jpc2 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/dependency-injection, and gives you the command that fixes it.

More advisories for symfony/dependency-injection

symfony/dependency-injection security overview

References

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