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

> Remote attackers can execute arbitrary code by tricking users into opening a malicious iim: URI that loads a DLL from a network share.

- **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:** 1 Oct 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-47gr-pfr8-r958

## What is CVE-2009-3518?

CVE-2009-3518 is a critical code injection vulnerability in n/a, published on 1 Oct 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

Argument injection vulnerability in the iim: URI handler in IBMIM.exe in IBM Installation Manager 1.3.2 and earlier, as used in IBM Rational Robot and Rational Team Concert, allows remote attackers to load arbitrary DLL files via the -vm option, as demonstrated by a reference to a UNC share pathname.

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

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

It affects 1 product.


Products: Ibm Installation Manager.

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

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

## Is CVE-2009-3518 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3518 exists.

Public exploit code:

- IBM Installation Manager 1.3.0 - 'iim://' URI handler (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2015-7442](https://insights.sbomify.com/CVE-2015-7442/): Privilege escalation in n/a (high 7.0)
- [CVE-2014-6134](https://insights.sbomify.com/CVE-2014-6134/): Information disclosure in n/a (low 1.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-3518 is a critical code injection vulnerability in n/a, published on 1 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3518 exists.

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-3518/ (Markdown: https://insights.sbomify.com/CVE-2009-3518/index.md)
```

## Sources

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

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