# CVE-2005-3134: Security feature bypass in n/a

> Remote attackers can bypass policy restrictions in Citrix Metaframe Presentation Server by modifying the client device name in the launch.ica file.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pmgf-6f22-vx8p

## What is CVE-2005-3134?

CVE-2005-3134 is a high-severity vulnerability in n/a, published on 4 Oct 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Citrix Metaframe Presentation Server 3.0 and 4.0 allows remote attackers to bypass policy restrictions by downloading the launch.ica file and changing the client device name (ClientName).

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

It affects 1 product.


Products: Citrix Metaframe.

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

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

## Is CVE-2005-3134 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-0244](https://insights.sbomify.com/CVE-2000-0244/): Weak cryptography in n/a (critical 10.0)
- [CVE-2006-5821](https://insights.sbomify.com/CVE-2006-5821/): Memory corruption in n/a (high 7.5)
- [CVE-2001-0908](https://insights.sbomify.com/CVE-2001-0908/): Information disclosure in n/a (high 7.5)
- [CVE-2007-0444](https://insights.sbomify.com/CVE-2007-0444/): Memory corruption in n/a (high 7.2)
- [CVE-2006-3779](https://insights.sbomify.com/CVE-2006-3779/): Privilege escalation in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3134 is a high-severity vulnerability in n/a, published on 4 Oct 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-3134 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-3134/ (Markdown: https://insights.sbomify.com/CVE-2005-3134/index.md)
```

## Sources

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

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