# CVE-2006-5465: Memory corruption in n/a > Remote attackers can execute arbitrary code via crafted UTF-8 inputs to PHP's htmlentities or htmlspecialchars functions due to a buffer overflow. - **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 Nov 2006 - **Updated:** 7 Aug 2024 - **Also known as:** GHSA-6vhv-2cm2-pw8c, RHSA-2006:0730, RHSA-2006:0731 ## What is CVE-2006-5465? CVE-2006-5465 is a high-severity memory corruption vulnerability in Php Php, published on 4 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Buffer overflow in PHP before 5.2.0 allows remote attackers to execute arbitrary code via crafted UTF-8 inputs to the (1) htmlentities or (2) htmlspecialchars functions. ## Which versions are affected by CVE-2006-5465? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `php` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.13 | | `php-devel` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.13 | | `php-imap` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.13 | | `php-ldap` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.13 | | `php-manual` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.13 | | `php-mysql` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.13 | | `php-odbc` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.13 | | `php-pgsql` | Red Hat:enterprise_linux:2.1::as | All versions | 0:4.1.2-2.13 | | `php` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.13 | | `php-devel` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.13 | | `php-imap` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.13 | | `php-ldap` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.13 | | `php-manual` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.13 | | `php-mysql` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.13 | | `php-odbc` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.13 | | `php-pgsql` | Red Hat:enterprise_linux:2.1::aw | All versions | 0:4.1.2-2.13 | | `php` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.13 | | `php-devel` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.13 | | `php-imap` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.13 | | `php-ldap` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.13 | | `php-manual` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.13 | | `php-mysql` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.13 | | `php-odbc` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.13 | | `php-pgsql` | Red Hat:enterprise_linux:2.1::es | All versions | 0:4.1.2-2.13 | | `php` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.13 | | `php-devel` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.13 | | `php-imap` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.13 | | `php-ldap` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.13 | | `php-manual` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.13 | | `php-mysql` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.13 | | `php-odbc` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.13 | | `php-pgsql` | Red Hat:enterprise_linux:2.1::ws | All versions | 0:4.1.2-2.13 | | `php` | Red Hat:enterprise_linux:3::as | All versions | 0:4.3.2-37.ent | | `php-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:4.3.2-37.ent | | `php-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:4.3.2-37.ent | | `php-imap` | Red Hat:enterprise_linux:3::as | All versions | 0:4.3.2-37.ent | | `php-ldap` | Red Hat:enterprise_linux:3::as | All versions | 0:4.3.2-37.ent | | `php-mysql` | Red Hat:enterprise_linux:3::as | All versions | 0:4.3.2-37.ent | | `php-odbc` | Red Hat:enterprise_linux:3::as | All versions | 0:4.3.2-37.ent | | `php-pgsql` | Red Hat:enterprise_linux:3::as | All versions | 0:4.3.2-37.ent | Products: Php Php. ## How do I fix CVE-2006-5465? Upgrade to a fixed version. ## Is CVE-2006-5465 being exploited? There is no known exploitation of CVE-2006-5465 in the wild and no public exploit code. ## 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-5465 and fix it if it is affected. What it is: CVE-2006-5465 is a high-severity memory corruption vulnerability in Php Php, published on 4 Nov 2006. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2006-5465 in the wild and no public exploit code. 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-5465/ (Markdown: https://insights.sbomify.com/CVE-2006-5465/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2006-5465 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-5465 - OSV: https://osv.dev/vulnerability/CVE-2006-5465 --- From sbomify Insights: https://insights.sbomify.com/CVE-2006-5465/ Summaries are generated and may contain mistakes; the official description above is the record.