CVE-2015-4050: ESI unauthorized access

Published May 26, 2015
·
Updated

CVE-2015-4050: ESI unauthorized access

Other sources

FragmentListener in the HttpKernel component in Symfony 2.3.19 through 2.3.28, 2.4.9 through 2.4.10, 2.5.4 through 2.5.11, and 2.6.0 through 2.6.7, when ESI or SSI support enabled, does not check if the controller attribute is set, which allows remote attackers to bypass URL signing and security rules by including (1) no hash or (2) an invalid hash in a request to /fragment.

FragmentListener in the HttpKernel component in Symfony 2.3.19 through 2.3.28, 2.4.9 through 2.4.10, 2.5.4 through 2.5.11, and 2.6.0 through 2.6.7, when ESI or SSI support enabled, does not check if the controller attribute is set, which allows remote attackers to bypass URL signing and security rules by including (1) no hash or (2) an invalid hash in a request to /fragment.

This issue has been fixed in Symfony 2.3.29, 2.5.12, and 2.6.8. Note that no fixes are provided for Symfony 2.4 as it's not maintained anymore.

Affected Software

45 affected componentsFixes available
composer/symfony/symfony>=2.3.19, <2.3.29, >=2.4.9, <2.5.0, >=2.5.4, <2.5.12, >=2.6.0, <2.6.8
composer/symfony/http-kernel>=2.3.19, <2.3.29, >=2.4.9, <2.5.0, >=2.5.4, <2.5.12, >=2.6.0, <2.6.8
composer/symfony/http-kernel>=2.4.9<=2.4.10
composer/symfony/symfony>=2.6.0<2.6.8
2.6.8
composer/symfony/symfony>=2.5.4<2.5.12
2.5.12
composer/symfony/symfony>=2.4.9<=2.4.10
composer/symfony/symfony>=2.3.19<2.3.29
2.3.29
composer/symfony/http-kernel>=2.6.0<2.6.8
2.6.8
composer/symfony/http-kernel>=2.5.4<2.5.12
2.5.12
composer/symfony/http-kernel>=2.3.19<2.3.29
2.3.29
SensioLabs Symfony=2.3.19
SensioLabs Symfony=2.3.20
SensioLabs Symfony=2.3.21
SensioLabs Symfony=2.3.22
SensioLabs Symfony=2.3.23
SensioLabs Symfony=2.3.24
SensioLabs Symfony=2.3.25
SensioLabs Symfony=2.3.26
SensioLabs Symfony=2.3.27
SensioLabs Symfony=2.3.28
SensioLabs Symfony=2.4.9
SensioLabs Symfony=2.4.10
SensioLabs Symfony=2.5.4
SensioLabs Symfony=2.5.5
SensioLabs Symfony=2.5.6
SensioLabs Symfony=2.5.7
SensioLabs Symfony=2.5.8
SensioLabs Symfony=2.5.9
SensioLabs Symfony=2.5.10
SensioLabs Symfony=2.5.11
SensioLabs Symfony=2.6.0
SensioLabs Symfony=2.6.1
SensioLabs Symfony=2.6.3
SensioLabs Symfony=2.6.4
SensioLabs Symfony=2.6.5
SensioLabs Symfony=2.6.6
SensioLabs Symfony=2.6.7
composer/symfony/symfony>=2.3.19, <2.3.29
2.3.29
composer/symfony/symfony>=2.4.9, <2.5.0
2.5.0
composer/symfony/symfony>=2.5.4, <2.5.12
2.5.12
composer/symfony/symfony>=2.6.0, <2.6.8
2.6.8
composer/symfony/http-kernel>=2.3.19, <2.3.29
2.3.29
composer/symfony/http-kernel>=2.4.9, <2.5.0
2.5.0
composer/symfony/http-kernel>=2.5.4, <2.5.12
2.5.12
composer/symfony/http-kernel>=2.6.0, <2.6.8
2.6.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.6.8
  2. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.5.12
  3. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.3.29
  4. Upgrade

    Upgrade composer/symfony/http-kernel to a version that resolves this vulnerability.

    Fixed in 2.6.8
  5. Upgrade

    Upgrade composer/symfony/http-kernel to a version that resolves this vulnerability.

    Fixed in 2.5.12
  6. Upgrade

    Upgrade composer/symfony/http-kernel to a version that resolves this vulnerability.

    Fixed in 2.3.29
  7. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.5.0
  8. Upgrade

    Upgrade composer/symfony/http-kernel to a version that resolves this vulnerability.

    Fixed in 2.5.0
  9. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 2.3.29
  10. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 2.5.12
  11. Upgrade

    Upgrade Symfony to a version that resolves this vulnerability.

    Fixed in 2.6.8

Event History

May 26, 2015
Advisory Published
11:55 PM
Data Sourced
via Packagist·11:55 PM
DescriptionSeverityAffected Software
Jun 2, 2015
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2015-4050?

CVE-2015-4050 has a medium severity level as it allows unauthorized access to some fragments when ESI or SSI support is enabled.

2

How do I fix CVE-2015-4050?

To fix CVE-2015-4050, upgrade to Symfony versions 2.3.29, 2.5.12, 2.6.8 or later.

3

What software is affected by CVE-2015-4050?

CVE-2015-4050 affects Symfony versions from 2.3.19 to 2.6.7, specifically 2.3.x, 2.4.x, 2.5.x, and 2.6.x series.

4

Can CVE-2015-4050 lead to remote code execution?

CVE-2015-4050 could potentially allow remote attackers to execute unauthorized code under certain configurations.

5

Is CVE-2015-4050 related to web application firewalls?

While CVE-2015-4050 does not directly involve web application firewalls, implementing such a firewall can help mitigate its impact.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203