# CVE-2004-1078: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in the Citrix client triggered by a malicious cached icon filename.

- **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:** No
- **Published:** 26 Apr 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9gcj-95cr-frx9

## What is CVE-2004-1078?

CVE-2004-1078 is a high-severity memory corruption vulnerability in n/a, published on 26 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

Stack-based buffer overflow in the client for Citrix Program Neighborhood Agent for Win32 8.00.24737 and earlier and Citrix MetaFrame Presentation Server client for WinCE before 8.33 allows remote attackers to execute arbitrary code via a long cached icon filename in the InName XML element.

## Which versions are affected by CVE-2004-1078?

It affects 2 products.


Products: Citrix Metaframe Client, Citrix Program Neighborhood Agent.

## How do I fix CVE-2004-1078?

No fix has been published for CVE-2004-1078 yet. Limit exposure of the affected software until one is available.

## Is CVE-2004-1078 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1077](https://insights.sbomify.com/CVE-2004-1077/): Other in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1078 and fix it if it is affected.

What it is: CVE-2004-1078 is a high-severity memory corruption vulnerability in n/a, published on 26 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-2004-1078 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-2004-1078/ (Markdown: https://insights.sbomify.com/CVE-2004-1078/index.md)
```

## Sources

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

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