# CVE-2009-3546: Memory corruption in n/a > Remote attackers can trigger buffer overflows or over-reads via crafted GD files, potentially leading to code execution or denial of service. - **Severity:** Critical 9.3 (`AV:N/AC:M/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:** 19 Oct 2009 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2009-3546, GHSA-w7xp-2c87-fchc, RHSA-2010:0003, ROOT-OS-DEBIAN-12-CVE-2009-3546 ## What is CVE-2009-3546? CVE-2009-3546 is a critical memory corruption vulnerability in Php Php, published on 19 Oct 2009. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The _gdGetColors function in gd_gd.c in PHP 5.2.11 and 5.3.x before 5.3.1, and the GD Graphics Library 2.x, does not properly verify a certain colorsTotal structure member, which might allow remote attackers to conduct buffer overflow or buffer over-read attacks via a crafted GD file, a different vulnerability than CVE-2009-3293. NOTE: some of these details are obtained from third party information. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2009-3546? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gd` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-progs` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-progs` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-progs` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd-progs` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.28-5.4E.el4_8.1 | | `gd` | Red Hat:enterprise_linux:5::client | All versions | 0:2.0.33-9.4.el5_4.2 | | `gd-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.0.33-9.4.el5_4.2 | | `gd-progs` | Red Hat:enterprise_linux:5::client | All versions | 0:2.0.33-9.4.el5_4.2 | | `gd` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.0.33-9.4.el5_4.2 | | `gd-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.0.33-9.4.el5_4.2 | | `gd-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.0.33-9.4.el5_4.2 | | `gd` | Red Hat:enterprise_linux:5::server | All versions | 0:2.0.33-9.4.el5_4.2 | | `gd-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.0.33-9.4.el5_4.2 | | `gd-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.0.33-9.4.el5_4.2 | | `gd-progs` | Red Hat:enterprise_linux:5::server | All versions | 0:2.0.33-9.4.el5_4.2 | Products: Libgd Gd Graphics Library, Php Php. ## How do I fix CVE-2009-3546? Upgrade to a fixed version. ## Is CVE-2009-3546 being exploited? There is no known exploitation of CVE-2009-3546 in the wild and no public exploit code. ## Other vulnerabilities in Php Php - [CVE-2007-3477](https://insights.sbomify.com/CVE-2007-3477/): Denial of service in n/a (medium 5.0) - [CVE-2007-3472](https://insights.sbomify.com/CVE-2007-3472/): Integer overflow in n/a (medium 4.3) - [CVE-2007-3473](https://insights.sbomify.com/CVE-2007-3473/): Denial of service in n/a (medium 4.3) - [CVE-2007-3474](https://insights.sbomify.com/CVE-2007-3474/): Memory corruption in n/a (low 2.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2009-3546 and fix it if it is affected. What it is: CVE-2009-3546 is a critical memory corruption vulnerability in Php Php, published on 19 Oct 2009. 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-2009-3546 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-2009-3546/ (Markdown: https://insights.sbomify.com/CVE-2009-3546/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2009-3546 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-3546 - OSV: https://osv.dev/vulnerability/CVE-2009-3546 --- From sbomify Insights: https://insights.sbomify.com/CVE-2009-3546/ Summaries are generated and may contain mistakes; the official description above is the record.