CVE-2012-6432
First published: Wed Dec 19 2012(Updated: )
Code execution vulnerability via the "internal" routes
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| composer/symfony/symfony | >=2.0.0<2.0.20>=2.1.0<2.1.5 | |
| composer/symfony/symfony | >=2.1.0<2.1.5 | 2.1.5 |
| composer/symfony/symfony | >=2.0.0<2.0.20 | 2.0.20 |
| composer/symfony/symfony | =2.2-dev | |
| 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.1.0 | |
| Symfony | =2.1.1 | |
| Symfony | =2.1.2 | |
| Symfony | =2.1.3 | |
| Symfony | =2.2-dev |
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-20-and-2-1-5-released
- https://nvd.nist.gov/vuln/detail/CVE-2012-6432
- http://symfony.com/blog/security-release-symfony-2-0-20-and-2-1-5-released
- https://github.com/advisories/GHSA-89cp-fvcc-hxh7 (Advisory)
- https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2012-6432.yaml
Frequently Asked Questions
What is the severity of CVE-2012-6432?
CVE-2012-6432 is considered a critical vulnerability due to the potential for remote code execution.
How do I fix CVE-2012-6432?
To fix CVE-2012-6432, you should upgrade to Symfony version 2.0.20 or 2.1.5 or later.
What software is affected by CVE-2012-6432?
CVE-2012-6432 affects Symfony versions 2.0.x before 2.0.20, 2.1.x before 2.1.5, and 2.2-dev.
What happens if CVE-2012-6432 is exploited?
If CVE-2012-6432 is exploited, attackers could gain access to arbitrary services through internal routes.
Is there a workaround for CVE-2012-6432?
While upgrading is the best solution, temporarily disabling internal routes may help mitigate the risk of CVE-2012-6432.
- collector/friends-of-php
- agent/type
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-89cp-fvcc-hxh7
- alias/CVE-2012-6432
- agent/software-canonical-lookup
- agent/weakness
- agent/severity
- agent/references
- agent/description
- collector/github-advisory
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-cve
- source/NVD
- agent/author
- 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.1.0
- version/symfony/2.1.1
- version/symfony/2.1.2
- version/symfony/2.1.3
- version/symfony/2.2-dev