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.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.7.38, 2.8.31, 3.2.14, 3.3.13
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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. When a form is submitted by the user, the request handler classes of the Form component merge POST data and uploaded files data into one array. This big array forms the data that are then bound to the form. At this stage there is no difference anymore between submitted POST data and uploaded files. A user can send a crafted HTTP request where the value of a "FileType" is sent as normal POST data that could be interpreted as a local file path on the server-side (for example, "file:///etc/passwd"). If the application did not perform any additional checks about the value submitted to the "FileType", the contents of the given file on the server could have been exposed to the attacker.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- symfony/formPackagist
From 2.7.0 · fixed in 2.7.38
- symfony/formPackagist
From 2.8.0 · fixed in 2.8.31
- symfony/formPackagist
From 3.0.0 · fixed in 3.2.14
- symfony/formPackagist
From 3.3.0 · fixed in 3.3.13
- symfony/symfonyPackagist
From 2.7.0 · fixed in 2.7.38
- symfony/symfonyPackagist
From 2.8.0 · fixed in 2.8.31
- symfony/symfonyPackagist
From 3.0.0 · fixed in 3.2.14
- symfony/symfonyPackagist
From 3.3.0 · fixed in 3.3.13