CVE-2015-4050: Symfony Incorrect Access Control

CVE-2015-4050 · Severity: info · Published 2022-05-17

Symfony Incorrect Access Control

Technologies: symfony/http-kernel (Packagist), symfony/symfony (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2015-4050 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2015-4050 being exploited in the wild.
How severe is CVE-2015-4050?
Informational severity, published 17 May 2022.
Which products and versions are affected?
symfony/http-kernel (Packagist) ECOSYSTEM:introduced=2.3.19,fixed=2.3.29; symfony/symfony (Packagist) ECOSYSTEM:introduced=2.3.19,fixed=2.3.29.
Is there a fix for CVE-2015-4050?
Yes. symfony/http-kernel (Packagist): upgrade to 2.3.29 or later; symfony/symfony (Packagist): upgrade to 2.3.29 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2015-4050?
Check whether you run symfony/http-kernel (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/http-kernel (Packagist): upgrade to 2.3.29 or later
    composer require symfony/http-kernel:^2.3.29
  • symfony/symfony (Packagist): upgrade to 2.3.29 or later
    composer require symfony/symfony:^2.3.29

Affected products

  • symfony/http-kernel (Packagist) ECOSYSTEM:introduced=2.3.19,fixed=2.3.29
  • symfony/symfony (Packagist) ECOSYSTEM:introduced=2.3.19,fixed=2.3.29

Identifiers

  • CVE-2015-4050
  • GHSA-qmqw-mpqp-mr54

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