Skip to content
Fencer Intel
high 7.5

CVE-2019-18888 json

Argument injection in a MimeTypeGuesser in Symfony

published 6y ago modified 4mo ago also GHSA-xhh6-956q-4q69 , EUVD-2019-0807

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. If an application passes unvalidated user input as the file for which MIME type validation should occur, then arbitrary arguments are passed to the underlying file command. This is related to symfony/http-foundation (and symfony/mime in 4.3.x).

Patch / fix

  • packagist symfony/http-foundation 2.8.52, 3.4.35, 4.2.12, 4.3.8
  • packagist symfony/mime 4.3.8
  • packagist symfony/symfony 2.8.52, 3.4.35, 4.2.12, 4.3.8
  • symfony Debian 14, Debian 13, Debian 12 4.3.8+dfsg-1

debian advisories DEBIAN-CVE-2019-18888

Is CVE-2019-18888 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

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
packagist symfony/http-foundation
>=2.0.0, <2.8.52
>=3.0.0, <3.4.35
>=4.0.0, <4.2.12
>=4.3.0, <4.3.8
2.8.52
3.4.35
4.2.12
4.3.8
packagist symfony/mime
>=4.3.0, <4.3.8
4.3.8
packagist symfony/symfony
>=2.0.0, <2.8.52
>=3.0.0, <3.4.35
>=4.0.0, <4.2.12
>=4.3.0, <4.3.8
2.8.52
3.4.35
4.2.12
4.3.8

Classification

Weakness
  • CWE-88 Improper Neutralization of Argument Delimiters in a Command
  • CWE-20 Improper Input Validation

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.