Bug 1620259 (CVE-2017-16654) - CVE-2017-16654 php-symfony: Directory Traversal in the Intl component
Summary: CVE-2017-16654 php-symfony: Directory Traversal in the Intl component
Alias: CVE-2017-16654
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1620260 1620261 1620262 1620263
TreeView+ depends on / blocked
Reported: 2018-08-22 20:30 UTC by Laura Pardo
Modified: 2019-09-29 14:56 UTC (History)
3 users (show)

Fixed In Version: symfony 2.7.38, symfony 2.8.31, symfony 3.2.14, symfony 3.3.13, symfony 3.4-BETA5, symfony 4.0-BETA5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-10 10:36:24 UTC

Attachments (Terms of Use)

Description Laura Pardo 2018-08-22 20:30:00 UTC
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. 


Comment 1 Laura Pardo 2018-08-22 20:30:47 UTC
Created php-symfony tracking bugs for this issue:

Affects: epel-7 [bug 1620261]
Affects: fedora-27 [bug 1620260]

Created php-symfony3 tracking bugs for this issue:

Affects: fedora-28 [bug 1620263]

Created php-symfony4 tracking bugs for this issue:

Affects: fedora-all [bug 1620262]

Comment 2 Product Security DevOps Team 2019-06-10 10:36:24 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.

Note You need to log in before you can comment on or make changes to this bug.