# CVE-2007-2356: Memory corruption in n/a > A stack-based buffer overflow in GIMP's SUNRAS plugin allows remote attackers to execute arbitrary code via a crafted RAS file. - **Severity:** Medium 6.8 (`AV:N/AC:M/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:** A user has to click or open something - **Fix available:** Yes - **Published:** 30 Apr 2007 - **Updated:** 7 Aug 2024 - **Also known as:** DEBIAN-CVE-2007-2356, DSA-1301-1, GHSA-8fv7-cr78-jp82, RHSA-2007:0343 ## What is CVE-2007-2356? CVE-2007-2356 is a medium-severity memory corruption vulnerability in Gimp Gimp, published on 30 Apr 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Stack-based buffer overflow in the set_color_table function in sunras.c in the SUNRAS plugin in Gimp 2.2.14 allows user-assisted remote attackers to execute arbitrary code via a crafted RAS file. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2007-2356? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gimp` | Red Hat:enterprise_linux:2.1::as | All versions | 1:1.2.1-7.1.el2_1 | | `gimp-devel` | Red Hat:enterprise_linux:2.1::as | All versions | 1:1.2.1-7.1.el2_1 | | `gimp-perl` | Red Hat:enterprise_linux:2.1::as | All versions | 1:1.2.1-7.1.el2_1 | | `gimp` | Red Hat:enterprise_linux:2.1::aw | All versions | 1:1.2.1-7.1.el2_1 | | `gimp-devel` | Red Hat:enterprise_linux:2.1::aw | All versions | 1:1.2.1-7.1.el2_1 | | `gimp-perl` | Red Hat:enterprise_linux:2.1::aw | All versions | 1:1.2.1-7.1.el2_1 | | `gimp` | Red Hat:enterprise_linux:2.1::es | All versions | 1:1.2.1-7.1.el2_1 | | `gimp-devel` | Red Hat:enterprise_linux:2.1::es | All versions | 1:1.2.1-7.1.el2_1 | | `gimp-perl` | Red Hat:enterprise_linux:2.1::es | All versions | 1:1.2.1-7.1.el2_1 | | `gimp` | Red Hat:enterprise_linux:2.1::ws | All versions | 1:1.2.1-7.1.el2_1 | | `gimp-devel` | Red Hat:enterprise_linux:2.1::ws | All versions | 1:1.2.1-7.1.el2_1 | | `gimp-perl` | Red Hat:enterprise_linux:2.1::ws | All versions | 1:1.2.1-7.1.el2_1 | | `gimp` | Red Hat:enterprise_linux:3::as | All versions | 1:1.2.3-20.3.el3 | | `gimp-devel` | Red Hat:enterprise_linux:3::as | All versions | 1:1.2.3-20.3.el3 | | `gimp-perl` | Red Hat:enterprise_linux:3::as | All versions | 1:1.2.3-20.3.el3 | | `gimp` | Red Hat:enterprise_linux:3::desktop | All versions | 1:1.2.3-20.3.el3 | | `gimp-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 1:1.2.3-20.3.el3 | | `gimp-perl` | Red Hat:enterprise_linux:3::desktop | All versions | 1:1.2.3-20.3.el3 | | `gimp` | Red Hat:enterprise_linux:3::es | All versions | 1:1.2.3-20.3.el3 | | `gimp-devel` | Red Hat:enterprise_linux:3::es | All versions | 1:1.2.3-20.3.el3 | | `gimp-perl` | Red Hat:enterprise_linux:3::es | All versions | 1:1.2.3-20.3.el3 | | `gimp` | Red Hat:enterprise_linux:3::ws | All versions | 1:1.2.3-20.3.el3 | | `gimp-devel` | Red Hat:enterprise_linux:3::ws | All versions | 1:1.2.3-20.3.el3 | | `gimp-perl` | Red Hat:enterprise_linux:3::ws | All versions | 1:1.2.3-20.3.el3 | | `gimp` | Red Hat:enterprise_linux:4::as | All versions | 1:2.0.5-6.2.el4 | | `gimp-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 1:2.0.5-6.2.el4 | | `gimp-devel` | Red Hat:enterprise_linux:4::as | All versions | 1:2.0.5-6.2.el4 | | `gimp` | Red Hat:enterprise_linux:4::desktop | All versions | 1:2.0.5-6.2.el4 | | `gimp-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 1:2.0.5-6.2.el4 | | `gimp-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 1:2.0.5-6.2.el4 | | `gimp` | Red Hat:enterprise_linux:4::es | All versions | 1:2.0.5-6.2.el4 | | `gimp-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 1:2.0.5-6.2.el4 | | `gimp-devel` | Red Hat:enterprise_linux:4::es | All versions | 1:2.0.5-6.2.el4 | | `gimp` | Red Hat:enterprise_linux:4::ws | All versions | 1:2.0.5-6.2.el4 | | `gimp-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 1:2.0.5-6.2.el4 | | `gimp-devel` | Red Hat:enterprise_linux:4::ws | All versions | 1:2.0.5-6.2.el4 | | `gimp` | Red Hat:enterprise_linux:5::client | All versions | 2:2.2.13-2.el5 | | `gimp-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 2:2.2.13-2.el5 | | `gimp-libs` | Red Hat:enterprise_linux:5::client | All versions | 2:2.2.13-2.el5 | | `gimp` | Red Hat:enterprise_linux:5::client_workstation | All versions | 2:2.2.13-2.el5 | Products: Gimp Gimp. ## How do I fix CVE-2007-2356? Apply the vendor's patch. ## Is CVE-2007-2356 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2356 exists. Public exploit code: - GIMP 2.2.14 - '.ras' SUNRAS Plugin Buffer Overflow (exploitdb) - GIMP 2.2.14 (Windows x86) - '.ras' Download/Execute Buffer Overflow (exploitdb) ## Other vulnerabilities in Gimp Gimp - [CVE-2010-4541](https://insights.sbomify.com/CVE-2010-4541/): Memory corruption in n/a (critical 9.3) - [CVE-2009-3909](https://insights.sbomify.com/CVE-2009-3909/): Integer overflow in n/a (critical 9.3) - [CVE-2009-1570](https://insights.sbomify.com/CVE-2009-1570/): Integer overflow in n/a (critical 9.3) - [CVE-2009-0723](https://insights.sbomify.com/CVE-2009-0723/): Integer overflow in n/a (critical 9.3) - [CVE-2009-0733](https://insights.sbomify.com/CVE-2009-0733/): Memory corruption in n/a (critical 9.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2007-2356 and fix it if it is affected. What it is: CVE-2007-2356 is a medium-severity memory corruption vulnerability in Gimp Gimp, published on 30 Apr 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-2356 exists. Affected product: Gimp Gimp. 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-2007-2356/ (Markdown: https://insights.sbomify.com/CVE-2007-2356/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2007-2356 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-2356 - OSV: https://osv.dev/vulnerability/CVE-2007-2356 --- From sbomify Insights: https://insights.sbomify.com/CVE-2007-2356/ Summaries are generated and may contain mistakes; the official description above is the record.