CVE-2014-6072: Symfony/symfony Symfony Cross-Site Request Forgery Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-v35g-4rrw-h4fw
CVSS 8.1
CWE-94
Published
Advisory Summary

CVE-2014-6072 is a HIGH (CVSS 8.1) symfony cross-site request forgery vulnerability vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting Symfony/symfony libraries in the Packagist ecosystem. The issue involves symfony cross-site request forgery vulnerability in the web profiler. Remediation is available by upgrading affected packages to version 2.3.19, 2.4.9, 2.5.4.

CVE-2014-6072 at a Glance

CVE Identifier CVE-2014-6072
GHSA Identifier GHSA-v35g-4rrw-h4fw
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-94: Improper Control of Generation of Code ('Code Injection')
Affected Product Symfony/symfony
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2014-6072

To remediate this vulnerability, upgrade all affected Symfony/symfony dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

symfony/symfony fixed: 2.3.19
Upgrade symfony/symfony to 2.3.19
symfony/symfony fixed: 2.4.9
Upgrade symfony/symfony to 2.4.9
symfony/symfony fixed: 2.5.4
Upgrade symfony/symfony to 2.5.4
symfony/web-profiler-bundle fixed: 2.3.19
Upgrade symfony/web-profiler-bundle to 2.3.19
symfony/web-profiler-bundle fixed: 2.4.9
Upgrade symfony/web-profiler-bundle to 2.4.9
symfony/web-profiler-bundle fixed: 2.5.4
Upgrade symfony/web-profiler-bundle to 2.5.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for symfony/symfony

How to Check if You Are Affected

To determine whether your application is affected by CVE-2014-6072, inspect your project dependencies for Symfony/symfony:

inspect dependencies for symfony/symfony

Analyze the terminal output to locate any version of Symfony/symfony in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.3.19), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-94: Improper Control of Generation of Code ('Code Injection'), where the product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. In Symfony/symfony, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

All 2.0.X, 2.1.X, 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony WebProfiler bundle are affected by this security issue. This issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.0, 2.1, and 2.2 as they are not maintained anymore. ### Description The Symfony Web Profiler is a great development tool, but it should not be enabled on production servers. If it is enabled in production, it must be properly secured so that only authorized people have access to it. Developers must be very cautious about this as the Web Profiler gives many sensitive information about a Symfony project and any attackers can exploit many of them. Just to name a few sensitive information: user logins, user cookies, executed SQL statements, ... That being said, the import/export feature of the web profiler is exploitable even if the Web Profiler is secured as the form to import a profiler is not protected against CSRF attacks. Combined with the fact that profiles are imported as a PHP serialized string, it makes your application vulnerable to code injection. ### Resolution As the import/export feature of the Web Profiler is not that useful, and because PHP `serialize/unserialize` functions have a long history of vulnerabilities, I decided to remove this feature from the Web interface and move it as CLI commands. If you were relying on this feature, you now need to use the `profiler:import` and `profiler:export` Symfony commands provided by the WebProfiler bundle from the command line interface. Those commands are not enabled by default and must be activated explicitly. For Symfony 2.4+, you can import them in your `app/config.yml` configuration file: ``` import: - { resource: "%kernel.root_dir%/../vendor/symfony/symfony/src/Symfony/Bundle/WebProfilerBundle/Resources/config/commands.xml" } ``` For Symfony 2.3, you can use the following snippet of code in `app/console`: ``` $kernel = new AppKernel($env, $debug); $application = new Application($kernel); if ($kernel->getContainer()->has('profiler')) { $profiler = $kernel->getContainer()->get('profiler'); $application->add(new ImportCommand($profiler)); $application->add(new ExportCommand($profiler)); } $application->run($input); ``` At this point, I want to reiterate that you should never enable the Symfony Web Profiler on your production servers as this is a development tool. And if you need to enable it, double-check that it is properly secured. The patch for this issue is available here: https://github.com/symfony/symfony/pull/11832

CVE-2014-6072 Affected Symfony/symfony Versions

6 component(s)
Fixed Versions:
2.3.192.4.92.5.4
Product / Package Ecosystem Affected Versions Fixed Version
symfony/symfony
Packagist
≥ 2.0.0
< 2.3.19
2.3.19
symfony/symfony
Packagist
≥ 2.4.0
< 2.4.9
2.4.9
symfony/symfony
Packagist
≥ 2.5.0
< 2.5.4
2.5.4
symfony/web-profiler-bundle
Packagist
≥ 2.0.0
< 2.3.19
2.3.19
symfony/web-profiler-bundle
Packagist
≥ 2.4.0
< 2.4.9
2.4.9
symfony/web-profiler-bundle
Packagist
≥ 2.5.0
< 2.5.4
2.5.4

References

Frequently Asked Questions

What is CVE-2014-6072?
CVE-2014-6072 is a security vulnerability in Symfony/symfony involving Symfony Cross-Site Request Forgery vulnerability in the Web Profiler under CWE-94: Improper Control of Generation of Code ('Code Injection').
Which Symfony/symfony versions are affected?
Affected versions include releases prior to 2.3.19, 2.4.9, 2.5.4 across affected packages: symfony/symfony, symfony/web-profiler-bundle.
What version fixes CVE-2014-6072?
Upgrading to 2.3.19, 2.4.9, 2.5.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is symfony/symfony affected?
Yes, symfony/symfony is affected in releases prior to 2.3.19, 2.4.9, 2.5.4. Upgrade your dependency to 2.3.19, 2.4.9, 2.5.4 or later.
Is symfony/web-profiler-bundle affected?
Yes, symfony/web-profiler-bundle is affected in releases prior to 2.3.19, 2.4.9, 2.5.4. Upgrade your dependency to 2.3.19, 2.4.9, 2.5.4 or later.
What is the CVSS score of CVE-2014-6072?
CVE-2014-6072 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2014-6072?
CVE-2014-6072 is classified under CWE-94: Improper Control of Generation of Code ('Code Injection') (The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.).
How can I check Packagist dependencies for CVE-2014-6072?
Run the dependency tree command: 'inspect dependencies for symfony/symfony'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v35g-4rrw-h4fw",
  "modified" : "2024-05-30T13:00:01Z",
  "published" : "2024-05-30T13:00:01Z",
  "aliases" : [ "CVE-2014-6072" ],
  "summary" : "Symfony Cross-Site Request Forgery vulnerability in the Web Profiler",
  "details" : "All 2.0.X, 2.1.X, 2.2.X, 2.3.X, 2.4.X, and 2.5.X versions of the Symfony WebProfiler bundle are affected by this security issue.\n\nThis issue has been fixed in Symfony 2.3.19, 2.4.9, and 2.5.4. Note that no fixes are provided for Symfony 2.0, 2.1, and 2.2 as they are not maintained anymore.\n\n### Description\nThe Symfony Web Profiler is a great development tool, but it should not be enabled on production servers. If it is enabled in production, it must be properly secured so that only authorized people have access to it. Developers must be very cautious about this as the Web Profiler gives many sensitive information about a Symfony project and any attackers can exploit many of them. Just to name a few sensitive information: user logins, user cookies, executed SQL statements, ...\n\nThat being said, the import/export feature of the web profiler is exploitable even if the Web Profiler is secured as the form to import a profiler is not protected against CSRF attacks. Combined with the fact that profiles are imported as a PHP serialized string, it makes your application vulnerable to code injection.\n\n### Resolution\nAs the import/export feature of the Web Profiler is not that useful, and because PHP `serialize/unserialize` functions have a long history of vulnerabilities, I decided to remove this feature from the Web interface and move it as CLI commands.\n\nIf you were relying on this feature, you now need to use the `profiler:import` and `profiler:export` Symfony commands provided by the WebProfiler bundle from the command line interface.\n\nThose commands are not enabled by default and must be activated explicitly. For Symfony 2.4+, you can import them in your `app/config.yml` configuration file:\n\n ```\nimport:\n    - { resource: \"%kernel.root_dir%/../vendor/symfony/symfony/src/Symfony/Bundle/WebProfilerBundle/Resources/config/commands.xml\" }\n```\nFor Symfony 2.3, you can use the following snippet of code in `app/console`:\n\n```\n$kernel = new AppKernel($env, $debug);\n$application = new Application($kernel);\nif ($kernel->getContainer()->has('profiler')) {\n    $profiler = $kernel->getContainer()->get('profiler');\n    $application->add(new ImportCommand($profiler));\n    $application->add(new ExportCommand($profiler));\n}\n$application->run($input);\n```\nAt this point, I want to reiterate that you should never enable the Symfony Web Profiler on your production servers as this is a development tool. And if you need to enable it, double-check that it is properly secured.\n\nThe patch for this issue is available here: https://github.com/symfony/symfony/pull/11832",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "symfony/symfony"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.3.19"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "symfony/symfony"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.4.0"
      }, {
        "fixed" : "2.4.9"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "symfony/symfony"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.5.0"
      }, {
        "fixed" : "2.5.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "symfony/web-profiler-bundle"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.3.19"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "symfony/web-profiler-bundle"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.4.0"
      }, {
        "fixed" : "2.4.9"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "symfony/web-profiler-bundle"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.5.0"
      }, {
        "fixed" : "2.5.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/symfony/symfony/pull/11832"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/symfony/symfony/commit/f38536ab79058f6a934426c41170256ba9623a02"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/symfony/web-profiler-bundle/commit/5b589ba83faf7eb20cec50725cd657075aebdd36"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2014-6072.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/web-profiler-bundle/CVE-2014-6072.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://symfony.com/cve-2014-6072"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-94" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-05-30T13:00:01Z",
    "nvd_published_at" : null
  }
}