CVE-2013-1348: Symphony Vulnerable to PHP Code Injection via YAML Parsing

CVE-2013-1348 · Severity: info · Published 2022-05-17

Symphony Vulnerable to PHP Code Injection via YAML Parsing

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

Quick answers

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

Affected products

  • symfony/symfony (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=2.0.22
  • symfony/yaml (Packagist) ECOSYSTEM:introduced=2.0.0,fixed=2.0.22

Identifiers

  • CVE-2013-1348
  • GHSA-2r5h-6r7v-5m7c

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