# CVE-2009-0218: Code injection in n/a

> Remote attackers can execute arbitrary code via an insecure method in the IntraLaunch ActiveX control, requiring user interaction to trigger.

- **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:** 13 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r37r-vm68-w9j8

## What is CVE-2009-0218?

CVE-2009-0218 is a critical code injection vulnerability in n/a, published on 13 Apr 2009. 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

Insecure method vulnerability in Particle Software IntraLaunch Application Launcher ActiveX control in IntraLaunch.ocx, as used in LDRA TBbrowse and possibly other products, allows remote attackers to execute arbitrary code via unknown vectors.

## Which versions are affected by CVE-2009-0218?

It affects 1 product.


Products: Particlesoftware Intralaunch.

## How do I fix CVE-2009-0218?

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

## Is CVE-2009-0218 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0218 and fix it if it is affected.

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

## Sources

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

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