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

> A buffer overflow in xloadimage allows attackers to execute arbitrary code via a malicious NIFF file, requiring user interaction to open the file.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2005-3195, DEBIAN-CVE-2005-3178, DSA-858-1, DSA-859-1, GHSA-g3j8-jppq-c6p4, RHSA-2005:802

## What is CVE-2005-3178?

CVE-2005-3178 is a medium-severity memory corruption vulnerability in n/a, published on 7 Oct 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in xloadimage 4.1 and earlier, and xli, might allow user-assisted attackers to execute arbitrary code via a long title name in a NIFF file, which triggers the overflow during (1) zoom, (2) reduce, or (3) rotate operations.

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xloadimage` | Red Hat:enterprise_linux:3::as | All versions | 0:4.1-36.RHEL3 |
| `xloadimage-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:4.1-36.RHEL3 |
| `xloadimage` | Red Hat:enterprise_linux:3::desktop | All versions | 0:4.1-36.RHEL3 |
| `xloadimage-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:4.1-36.RHEL3 |
| `xloadimage` | Red Hat:enterprise_linux:3::es | All versions | 0:4.1-36.RHEL3 |
| `xloadimage-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:4.1-36.RHEL3 |
| `xloadimage` | Red Hat:enterprise_linux:3::ws | All versions | 0:4.1-36.RHEL3 |
| `xloadimage-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:4.1-36.RHEL3 |
| `xloadimage` | Red Hat:enterprise_linux:4::as | All versions | 0:4.1-36.RHEL4 |
| `xloadimage-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:4.1-36.RHEL4 |
| `xloadimage` | Red Hat:enterprise_linux:4::desktop | All versions | 0:4.1-36.RHEL4 |
| `xloadimage-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:4.1-36.RHEL4 |
| `xloadimage` | Red Hat:enterprise_linux:4::es | All versions | 0:4.1-36.RHEL4 |
| `xloadimage-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:4.1-36.RHEL4 |
| `xloadimage` | Red Hat:enterprise_linux:4::ws | All versions | 0:4.1-36.RHEL4 |
| `xloadimage-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:4.1-36.RHEL4 |

Products: Xli Xli, Xloadimage Xloadimage.

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

Apply the vendor's patch.

## Is CVE-2005-3178 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0775](https://insights.sbomify.com/CVE-2001-0775/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3178 is a medium-severity memory corruption vulnerability in n/a, published on 7 Oct 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-3178 in the wild and no public exploit code.

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

## Sources

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

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