Skip to content
Fencer Intel
medium 6.5

CVE-2017-16790 json

Symfony SSRF Vulnerability via Form Component

published 8y ago modified 4mo ago also GHSA-cqqh-94r6-wjrg , EUVD-2022-3618

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

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.

Patch / fix

  • packagist symfony/form 2.7.38, 2.8.31, 3.2.14, 3.3.13
  • packagist symfony/symfony 2.7.38, 2.8.31, 3.2.14, 3.3.13
  • symfony Debian 14, Debian 13, Debian 12 3.4.0+dfsg-1

debian advisories DEBIAN-CVE-2017-16790

Is CVE-2017-16790 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-16790 updated cvss 5.3

php-symfony: Information Exposure due to an improper check of FileType on submitted data

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.57% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist symfony/form
>=2.7.0, <2.7.38
>=2.8.0, <2.8.31
>=3.0.0, <3.2.14
>=3.3.0, <3.3.13
2.7.38
2.8.31
3.2.14
3.3.13
packagist symfony/symfony
>=2.7.0, <2.7.38
>=2.8.0, <2.8.31
>=3.0.0, <3.2.14
>=3.3.0, <3.3.13
2.7.38
2.8.31
3.2.14
3.3.13

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.