# CVE-2005-1046: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted PCX image file in KDE applications.

- **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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-714-1, GHSA-m4qw-p9hj-gqw8, RHSA-2005:393

## What is CVE-2005-1046?

CVE-2005-1046 is a high-severity memory corruption vulnerability in Kde Kde, published on 12 Apr 2005. 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

Buffer overflow in the kimgio library for KDE 3.4.0 allows remote attackers to execute arbitrary code via a crafted PCX image file.

## Which versions are affected by CVE-2005-1046?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kdelibs` | Red Hat:enterprise_linux:4::as | All versions | 6:3.3.1-3.10 |
| `kdelibs-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 6:3.3.1-3.10 |
| `kdelibs-devel` | Red Hat:enterprise_linux:4::as | All versions | 6:3.3.1-3.10 |
| `kdelibs` | Red Hat:enterprise_linux:4::desktop | All versions | 6:3.3.1-3.10 |
| `kdelibs-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 6:3.3.1-3.10 |
| `kdelibs-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 6:3.3.1-3.10 |
| `kdelibs` | Red Hat:enterprise_linux:4::es | All versions | 6:3.3.1-3.10 |
| `kdelibs-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 6:3.3.1-3.10 |
| `kdelibs-devel` | Red Hat:enterprise_linux:4::es | All versions | 6:3.3.1-3.10 |
| `kdelibs` | Red Hat:enterprise_linux:4::ws | All versions | 6:3.3.1-3.10 |
| `kdelibs-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 6:3.3.1-3.10 |
| `kdelibs-devel` | Red Hat:enterprise_linux:4::ws | All versions | 6:3.3.1-3.10 |

Products: Kde Kde.

## How do I fix CVE-2005-1046?

Apply the vendor's patch.

## Is CVE-2005-1046 being exploited?

There is no known exploitation of CVE-2005-1046 in the wild and no public exploit code.

## Other vulnerabilities in Kde Kde

- [CVE-2005-0011](https://insights.sbomify.com/CVE-2005-0011/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0690](https://insights.sbomify.com/CVE-2003-0690/): Privilege escalation in n/a (critical 10.0)
- [CVE-2008-1670](https://insights.sbomify.com/CVE-2008-1670/): Memory corruption in n/a (critical 9.3)
- [CVE-2012-4512](https://insights.sbomify.com/CVE-2012-4512/): Memory corruption in Konqueror (high 8.8)
- [CVE-2006-0019](https://insights.sbomify.com/CVE-2006-0019/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1046 and fix it if it is affected.

What it is: CVE-2005-1046 is a high-severity memory corruption vulnerability in Kde Kde, published on 12 Apr 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-1046 in the wild and no public exploit code.

Affected product: Kde Kde. 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-2005-1046/ (Markdown: https://insights.sbomify.com/CVE-2005-1046/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-1046
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-1046
- OSV: https://osv.dev/vulnerability/CVE-2005-1046

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-1046/
Summaries are generated and may contain mistakes; the official description above is the record.