CVE-2017-16654: Intl bundle readers breaking out of paths

Published Nov 16, 2017
·
Updated

An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The Intl component includes various bundle readers that are used to read resource bundles from the local filesystem. The read() methods of these classes use a path and a locale to determine the language bundle to retrieve. The locale argument value is commonly retrieved from untrusted user input (like a URL parameter). An attacker can use this argument to navigate to arbitrary directories via the dot-dot-slash attack, aka Directory Traversal.

Other sources

CVE-2017-16654: Intl bundle readers breaking out of paths

Affected Software

29 affected componentsFixes available
composer/symfony/symfony>=2.7.0, <2.7.38, >=2.8.0, <2.8.31, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.2.14, >=3.3.0, <3.3.13
composer/symfony/intl>=2.7.0, <2.7.38, >=2.8.0, <2.8.31, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.2.14, >=3.3.0, <3.3.13
debian/symfony
3.4.22+dfsg-2+deb10u13.4.22+dfsg-2+deb10u24.4.19+dfsg-2+deb11u35.4.23+dfsg-15.4.29+dfsg-15.4.30+dfsg-1
composer/symfony/symfony>=3.3.0<3.3.13
3.3.13
composer/symfony/symfony>=3.0.0<3.2.14
3.2.14
composer/symfony/symfony>=2.8.0<2.8.31
2.8.31
composer/symfony/symfony>=2.7.0<2.7.38
2.7.38
composer/symfony/intl>=3.3.0<3.3.13
3.3.13
composer/symfony/intl>=3.0.0<3.2.14
3.2.14
composer/symfony/intl>=2.8.0<2.8.31
2.8.31
composer/symfony/intl>=2.7.0<2.7.38
2.7.38
SensioLabs Symfony>=2.7.0<=2.7.37
SensioLabs Symfony>=3.2.0<=3.2.13
SensioLabs Symfony>=3.3.0<=3.3.12
SensioLabs Symfony>=3.8.0<=3.8.30
Debian Debian Linux=8.0
Debian Debian Linux=9.0
composer/symfony/symfony>=2.7.0, <2.7.38
2.7.38
composer/symfony/symfony>=2.8.0, <2.8.31
2.8.31
composer/symfony/symfony>=3.0.0, <3.1.0
composer/symfony/symfony>=3.1.0, <3.2.0
composer/symfony/symfony>=3.2.0, <3.2.14
3.2.14
composer/symfony/symfony>=3.3.0, <3.3.13
3.3.13
composer/symfony/intl>=2.7.0, <2.7.38
2.7.38
composer/symfony/intl>=2.8.0, <2.8.31
2.8.31
composer/symfony/intl>=3.0.0, <3.1.0
composer/symfony/intl>=3.1.0, <3.2.0
composer/symfony/intl>=3.2.0, <3.2.14
3.2.14
composer/symfony/intl>=3.3.0, <3.3.13
3.3.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 3.4.22+dfsg-2+deb10u1Fixed in 3.4.22+dfsg-2+deb10u2Fixed in 4.4.19+dfsg-2+deb11u3Fixed in 5.4.23+dfsg-1Fixed in 5.4.29+dfsg-1Fixed in 5.4.30+dfsg-1
  2. Upgrade

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

    Fixed in 3.3.13
  3. Upgrade

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

    Fixed in 3.2.14
  4. Upgrade

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

    Fixed in 2.8.31
  5. Upgrade

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

    Fixed in 2.7.38
  6. Upgrade

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

    Fixed in 3.3.13
  7. Upgrade

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

    Fixed in 3.2.14
  8. Upgrade

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

    Fixed in 2.8.31
  9. Upgrade

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

    Fixed in 2.7.38

Event History

Nov 16, 2017
Advisory Published
via Packagist·03:15 PM
Data Sourced
via Packagist·03:15 PM
DescriptionSeverityAffected Software
Advisory Published
03:24 PM
Aug 6, 2018
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description

Frequently Asked Questions

1

What is CVE-2017-16654?

CVE-2017-16654 is a vulnerability in the Symfony framework that allows potential path traversal attacks.

2

What is the severity level of CVE-2017-16654?

The severity level of CVE-2017-16654 is high with a CVSS score of 7.5.

3

Which versions of Symfony are affected by CVE-2017-16654?

Versions before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5 of Symfony are affected.

4

How can I fix CVE-2017-16654?

To fix CVE-2017-16654, update your Symfony framework to version 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, or 4.0-BETA5.

5

Where can I find more information about CVE-2017-16654?

You can find more information about CVE-2017-16654 on the National Vulnerability Database (NVD) website and the GitHub pull request.

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