CVE-2018-19789: Symfony Path Disclosure

CVE-2018-19789 · Severity: low · CVSS 3 · Published 2022-05-14

Symfony Path Disclosure

Technologies: symfony/form (Packagist), symfony/symfony (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2018-19789 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-19789 being exploited in the wild.
How severe is CVE-2018-19789?
Low severity, with a CVSS score of 3, published 14 May 2022.
Which products and versions are affected?
symfony/form (Packagist) ECOSYSTEM:introduced=2.7.0,fixed=2.7.50; symfony/symfony (Packagist) ECOSYSTEM:introduced=2.7.0,fixed=2.7.50.
Is there a fix for CVE-2018-19789?
Yes. symfony/form (Packagist): upgrade to 2.7.50 or later; symfony/symfony (Packagist): upgrade to 2.7.50 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-19789?
Check whether you run symfony/form (Packagist) or symfony/symfony (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • symfony/form (Packagist): upgrade to 2.7.50 or later
    composer require symfony/form:^2.7.50
  • symfony/symfony (Packagist): upgrade to 2.7.50 or later
    composer require symfony/symfony:^2.7.50

Affected products

  • symfony/form (Packagist) ECOSYSTEM:introduced=2.7.0,fixed=2.7.50
  • symfony/symfony (Packagist) ECOSYSTEM:introduced=2.7.0,fixed=2.7.50

Identifiers

  • CVE-2018-19789
  • GHSA-x3cf-w64x-4cp2

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.