CVE-2013-1348: Code Injection
First published: Tue Jan 15 2013(Updated: )
Ability to enable/disable PHP parsing in Yaml::parse()
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| composer/symfony/symfony | >=2.0.0<2.0.22 | |
| composer/symfony/yaml | >=2.0.0<2.0.22 | |
| composer/symfony/yaml | >=2.0.0<2.0.22 | 2.0.22 |
| composer/symfony/symfony | >=2.0.0<2.0.22 | 2.0.22 |
| Symfony | =2.0.0 | |
| Symfony | =2.0.1 | |
| Symfony | =2.0.2 | |
| Symfony | =2.0.3 | |
| Symfony | =2.0.4 | |
| Symfony | =2.0.5 | |
| Symfony | =2.0.6 | |
| Symfony | =2.0.7 | |
| Symfony | =2.0.8 | |
| Symfony | =2.0.9 | |
| Symfony | =2.0.10 | |
| Symfony | =2.0.11 | |
| Symfony | =2.0.12 | |
| Symfony | =2.0.13 | |
| Symfony | =2.0.14 | |
| Symfony | =2.0.15 | |
| Symfony | =2.0.16 | |
| Symfony | =2.0.17 | |
| Symfony | =2.0.18 | |
| Symfony | =2.0.19 | |
| Symfony | =2.0.20 | |
| Symfony | =2.0.21 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://symfony.com/blog/security-release-symfony-2-0-22-and-2-1-7-released
- http://secunia.com/advisories/51980
- http://symfony.com/blog/security-release-symfony-2-0-22-and-2-1-7-released
- http://www.securityfocus.com/bid/57574
- https://exchange.xforce.ibmcloud.com/vulnerabilities/81550
- https://nvd.nist.gov/vuln/detail/CVE-2013-1348
- https://github.com/symfony/symfony/commit/ac756bf39e646b4e130fad058d10a0228dbd9779
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2013-1348.yaml
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/yaml/CVE-2013-1348.yaml
- https://web.archive.org/web/20150612022223/http://www.securityfocus.com/bid/57574
- https://github.com/advisories/GHSA-2r5h-6r7v-5m7c (Advisory)
Frequently Asked Questions
What is the severity of CVE-2013-1348?
CVE-2013-1348 is considered a critical vulnerability due to its potential to allow remote code execution.
How do I fix CVE-2013-1348?
To fix CVE-2013-1348, you should upgrade your Symfony version to 2.0.22 or later.
Which Symfony versions are affected by CVE-2013-1348?
CVE-2013-1348 affects Symfony versions from 2.0.0 up to 2.0.21.
Can CVE-2013-1348 be exploited remotely?
Yes, CVE-2013-1348 can be exploited remotely by attackers to execute arbitrary PHP code.
Is CVE-2013-1348 related to any other vulnerabilities?
CVE-2013-1348 is related to CVE-2013-1397 but addresses a different issue regarding PHP code execution.
- collector/friends-of-php
- agent/type
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-2r5h-6r7v-5m7c
- alias/CVE-2013-1348
- agent/software-canonical-lookup
- agent/references
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/softwarecombine
- agent/description
- agent/event
- agent/author
- collector/github-advisory
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-cve
- source/NVD
- package-manager/composer
- vendor/sensiolabs
- canonical/symfony
- version/symfony/2.0.0
- version/symfony/2.0.1
- version/symfony/2.0.2
- version/symfony/2.0.3
- version/symfony/2.0.4
- version/symfony/2.0.5
- version/symfony/2.0.6
- version/symfony/2.0.7
- version/symfony/2.0.8
- version/symfony/2.0.9
- version/symfony/2.0.10
- version/symfony/2.0.11
- version/symfony/2.0.12
- version/symfony/2.0.13
- version/symfony/2.0.14
- version/symfony/2.0.15
- version/symfony/2.0.16
- version/symfony/2.0.17
- version/symfony/2.0.18
- version/symfony/2.0.19
- version/symfony/2.0.20
- version/symfony/2.0.21