| パッケージ | 影響を受けるバージョン | 修正済みバージョン |
|---|---|---|
| symfony/http-kernel | ≥ 2.0.0, < 2.3.27≥ 2.4.0, < 2.5.11≥ 2.6.0, < 2.6.6 | 2.3.272.5.112.6.6 |
| symfony/symfony | ≥ 2.0.0, < 2.3.27≥ 2.4.0, < 2.5.11≥ 2.6.0, < 2.6.6 | 2.3.272.5.112.6.6 |
| symfony | = 2.0.0= 2.0.1= 2.0.10= 2.0.11= 2.0.12= 2.0.13= 2.0.14= 2.0.15= 2.0.16= 2.0.17= 2.0.18= 2.0.19= 2.0.2= 2.0.20= 2.0.21= 2.0.22= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.8= 2.0.9= 2.1.0= 2.1.1= 2.1.2= 2.1.3= 2.1.4= 2.1.5= 2.1.6= 2.1.7= 2.2.0= 2.2.1= 2.2.10= 2.2.11= 2.2.2= 2.2.3= 2.2.4= 2.2.5= 2.2.6= 2.2.8= 2.2.9= 2.3.19= 2.3.20= 2.3.21= 2.3.22= 2.3.23= 2.3.24= 2.3.25= 2.3.26= 2.4.1= 2.4.10= 2.4.2= 2.4.3= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9= 2.5.1= 2.5.10= 2.5.2= 2.5.3= 2.5.4= 2.5.5= 2.5.6= 2.5.7= 2.5.8= 2.5.9= 2.6.0= 2.6.1= 2.6.3= 2.6.4= 2.6.5 |
Applications with ESI support (and SSI support as of Symfony 2.6) enabled and using the Symfony built-in reverse proxy (the `Symfony\Component\HttpKernel\HttpCache class) are vulnerable to PHP code injection; a malicious user can inject PHP code that will be executed by the server.
HttpCache uses eval() to execute files in its cache when they contain ESI tags (and only when ESI is enabled). The vulnerability comes from the fact that PHP allows contents of <script language="php"> tags to be executed (and this kind of PHP tags is always available regardless of the configuration), but there were not escaped before the evaluation.
A possible exploit comes from websites also vulnerable to Cross-Site Scripting as an attacker can successfully conduct a PHP code injection attack by passing such a tag in a user submitted variable (for which proper output escaping was not applied).
これらの製品をお使いですか?サイトをスキャンして、脆弱なバージョンが公開されていないか確認しましょう。
無料でサイトをスキャン