CVE-2017-11365: Symfony Incorrect Access Control

Quick answers

Is CVE-2017-11365 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2017-11365 being exploited in the wild.

How severe is CVE-2017-11365?

Low severity, with a CVSS score of 3, published 24 May 2022.

Which products and versions are affected?

symfony/security (Packagist) ECOSYSTEM:introduced=2.7.30,fixed=2.7.32; symfony/security-core (Packagist) ECOSYSTEM:introduced=2.7.30,fixed=2.7.32; symfony/symfony (Packagist) ECOSYSTEM:introduced=2.7.30,fixed=2.7.32.

Is there a fix for CVE-2017-11365?

Yes. symfony/security (Packagist): upgrade to 2.7.32 or later; symfony/security-core (Packagist): upgrade to 2.7.32 or later; symfony/symfony (Packagist): upgrade to 2.7.32 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2017-11365?

Check whether you run symfony/security (Packagist), symfony/security-core (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/security (Packagist): upgrade to 2.7.32 or later

  composer require symfony/security:^2.7.32

• symfony/security-core (Packagist): upgrade to 2.7.32 or later

  composer require symfony/security-core:^2.7.32

• symfony/symfony (Packagist): upgrade to 2.7.32 or later

  composer require symfony/symfony:^2.7.32

Affected products

• symfony/security (Packagist) ECOSYSTEM:introduced=2.7.30,fixed=2.7.32
• symfony/security-core (Packagist) ECOSYSTEM:introduced=2.7.30,fixed=2.7.32
• symfony/symfony (Packagist) ECOSYSTEM:introduced=2.7.30,fixed=2.7.32

Identifiers

• CVE-2017-11365
• GHSA-q87v-q8fw-gmj5