# CVE-2006-4812: Integer overflow in n/a > Remote attackers can execute arbitrary code via integer overflow in PHP's unserialize function, affecting web applications using vulnerable PHP versions. - **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Oct 2006 - **Updated:** 7 Aug 2024 - **Also known as:** CVE-2006-4170, GHSA-2g5f-835h-7qjr, RHSA-2006:0708 ## What is CVE-2006-4812? CVE-2006-4812 is a critical vulnerability in Php Php, published on 9 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Integer overflow in PHP 5 up to 5.1.6 and 4 before 4.3.0 allows remote attackers to execute arbitrary code via an argument to the unserialize PHP function with a large value for the number of array elements, which triggers the overflow in the Zend Engine ecalloc function (Zend/zend_alloc.c). Weakness: CWE-94 (Improper Control of Generation of Code) ## Which versions are affected by CVE-2006-4812? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `php` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.12 | | `php-devel` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.12 | | `php-imap` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.12 | | `php-ldap` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.12 | | `php-manual` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.12 | | `php-mysql` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.12 | | `php-odbc` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.12 | | `php-pgsql` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.12 | | `php` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.12 | | `php-devel` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.12 | | `php-imap` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.12 | | `php-ldap` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.12 | | `php-manual` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.12 | | `php-mysql` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.12 | | `php-odbc` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.12 | | `php-pgsql` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.12 | | `php` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.12 | | `php-devel` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.12 | | `php-imap` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.12 | | `php-ldap` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.12 | | `php-manual` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.12 | | `php-mysql` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.12 | | `php-odbc` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.12 | | `php-pgsql` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.12 | | `php` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.12 | | `php-devel` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.12 | | `php-imap` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.12 | | `php-ldap` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.12 | | `php-manual` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.12 | | `php-mysql` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.12 | | `php-odbc` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.12 | | `php-pgsql` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.12 | Products: Php Php. ## How do I fix CVE-2006-4812? Upgrade to a fixed version. ## Is CVE-2006-4812 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4812 exists. Public exploit code: - PHP 3 < 5 - ZendEngine ECalloc Integer Overflow (exploitdb) ## Other vulnerabilities in Php Php - [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0) - [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0) - [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0) - [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0) - [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2006-4812 and fix it if it is affected. What it is: CVE-2006-4812 is a critical vulnerability in Php Php, published on 9 Oct 2006. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4812 exists. Affected product: Php Php. No package-level version data is available, so check the vendor advisory linked from the reference page. 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-2006-4812/ (Markdown: https://insights.sbomify.com/CVE-2006-4812/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2006-4812 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-4812 - OSV: https://osv.dev/vulnerability/CVE-2006-4812 --- From sbomify Insights: https://insights.sbomify.com/CVE-2006-4812/ Summaries are generated and may contain mistakes; the official description above is the record.