# CVE-2013-4751: Symfony collectionCascaded and collectionCascadedDeeply fields security bypass > The Symfony Validator library loses information during serialization, potentially allowing attackers to modify data integrity. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Nov 2019 - **Updated:** 6 Aug 2024 - **Also known as:** GHSA-q8j7-fjh7-25v5 ## What is CVE-2013-4751? CVE-2013-4751 is a high-severity unsafe deserialization vulnerability in Fedoraproject Fedora, published on 1 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description php-symfony2-Validator has loss of information during serialization Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2013-4751? 16 open source packages ship an affected version, including symfony/symfony and symfony/validator. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `symfony/symfony` | Packagist | From 2.0.0 | 2.0.24 | | `symfony/symfony` | Packagist | From 2.0.0 | 2.0.24 | | `symfony/symfony` | Packagist | From 2.1.0 | 2.1.12 | | `symfony/symfony` | Packagist | From 2.1.0 | 2.1.12 | | `symfony/symfony` | Packagist | From 2.2.0 | 2.2.5 | | `symfony/symfony` | Packagist | From 2.2.0 | 2.2.5 | | `symfony/symfony` | Packagist | From 2.3.0 | 2.3.3 | | `symfony/symfony` | Packagist | From 2.3.0 | 2.3.3 | | `symfony/validator` | Packagist | From 2.0.0 | 2.0.24 | | `symfony/validator` | Packagist | From 2.0.0 | 2.0.24 | | `symfony/validator` | Packagist | From 2.1.0 | 2.1.12 | | `symfony/validator` | Packagist | From 2.1.0 | 2.1.12 | | `symfony/validator` | Packagist | From 2.2.0 | 2.2.5 | | `symfony/validator` | Packagist | From 2.2.0 | 2.2.5 | | `symfony/validator` | Packagist | From 2.3.0 | 2.3.3 | | `symfony/validator` | Packagist | From 2.3.0 | 2.3.3 | Products: Fedoraproject Fedora, Redhat Enterprise Linux, Sensiolabs Symfony. ## How do I fix CVE-2013-4751? Upgrade symfony/symfony to a fixed version for your release line: 2.0.24, 2.1.12, 2.2.5 or 2.3.3. ## Is CVE-2013-4751 being exploited? There is no known exploitation of CVE-2013-4751 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild) - [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild) - [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2013-4751 and fix it if it is affected. What it is: CVE-2013-4751 is a high-severity unsafe deserialization vulnerability in Fedoraproject Fedora, published on 1 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2013-4751 in the wild and no public exploit code. Affected packages and fixed versions: - symfony/symfony (Packagist): affected from 2.0.0; fixed in 2.0.24 - symfony/symfony (Packagist): affected from 2.0.0; fixed in 2.0.24 - symfony/symfony (Packagist): affected from 2.1.0; fixed in 2.1.12 - symfony/symfony (Packagist): affected from 2.1.0; fixed in 2.1.12 - symfony/symfony (Packagist): affected from 2.2.0; fixed in 2.2.5 - symfony/symfony (Packagist): affected from 2.2.0; fixed in 2.2.5 - symfony/symfony (Packagist): affected from 2.3.0; fixed in 2.3.3 - symfony/symfony (Packagist): affected from 2.3.0; fixed in 2.3.3 - symfony/validator (Packagist): affected from 2.0.0; fixed in 2.0.24 - symfony/validator (Packagist): affected from 2.0.0; fixed in 2.0.24 - symfony/validator (Packagist): affected from 2.1.0; fixed in 2.1.12 - symfony/validator (Packagist): affected from 2.1.0; fixed in 2.1.12 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2013-4751/ (Markdown: https://insights.sbomify.com/CVE-2013-4751/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4751 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4751 - OSV: https://osv.dev/vulnerability/CVE-2013-4751 --- From sbomify Insights: https://insights.sbomify.com/CVE-2013-4751/ Summaries are generated and may contain mistakes; the official description above is the record.