# CVE-2010-2991: Code injection in n/a

> Remote attackers can execute arbitrary code or cause denial of service via a crafted HTML document triggering the Citrix ICA Client ActiveX object.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** 11 Aug 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-x85q-ch42-gg6w

## What is CVE-2010-2991?

CVE-2010-2991 is a critical code injection vulnerability in n/a, published on 11 Aug 2010. 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

The IICAClient interface in the ICAClient library in the ICA Client ActiveX Object (aka ICO) component in Citrix Online Plug-in for Windows for XenApp & XenDesktop before 12.0.3 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted HTML document that triggers the reading of a .ICA file.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2010-2991?

It affects 1 product.


Products: Citrix Online Plug-in for Windows for Xenapp \& Xendesktop.

## How do I fix CVE-2010-2991?

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

## Is CVE-2010-2991 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2991 and fix it if it is affected.

What it is: CVE-2010-2991 is a critical code injection vulnerability in n/a, published on 11 Aug 2010. 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-2010-2991 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-2010-2991/ (Markdown: https://insights.sbomify.com/CVE-2010-2991/index.md)
```

## Sources

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

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