# CVE-2008-3075: Command injection in n/a

> Attackers can execute arbitrary code via malicious ZIP filenames in Vim due to improper shell escaping, requiring user interaction to open the file.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-3075, GHSA-wqmg-q854-x6x6

## What is CVE-2008-3075?

CVE-2008-3075 is a critical command injection vulnerability in Vim Vim, published on 21 Feb 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The shellescape function in Vim 7.0 through 7.2, including 7.2a.10, allows user-assisted attackers to execute arbitrary code via the "!" (exclamation point) shell metacharacter in (1) the filename of a ZIP archive and possibly (2) the filename of the first file in a ZIP archive, which is not properly handled by zip.vim in the VIM ZIP plugin (zipPlugin.vim) v.11 through v.21, as demonstrated by the zipplugin and zipplugin.v2 test cases.  NOTE: this issue reportedly exists because of an incomplete fix for CVE-2008-2712.  NOTE: this issue has the same root cause as CVE-2008-3074.  NOTE: due to the complexity of the associated disclosures and the incomplete information related to them, there may be inaccuracies in this CVE description and in external mappings to this identifier.

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

## Which versions are affected by CVE-2008-3075?

It affects 2 products.


Products: Vim Vim, Vim Zipplugin.vim.

## How do I fix CVE-2008-3075?

Upgrade to a fixed version.

## Is CVE-2008-3075 being exploited?

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

## Other vulnerabilities in Vim Vim

- [CVE-2020-20703](https://insights.sbomify.com/CVE-2020-20703/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-6349](https://insights.sbomify.com/CVE-2017-6349/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-6350](https://insights.sbomify.com/CVE-2017-6350/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-5953](https://insights.sbomify.com/CVE-2017-5953/): Integer overflow in n/a (critical 9.8)
- [CVE-2008-3076](https://insights.sbomify.com/CVE-2008-3076/): Command injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3075 and fix it if it is affected.

What it is: CVE-2008-3075 is a critical command injection vulnerability in Vim Vim, published on 21 Feb 2009. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-3075 in the wild and no public exploit code.

Affected product: Vim Vim. 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-2008-3075/ (Markdown: https://insights.sbomify.com/CVE-2008-3075/index.md)
```

## Sources

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

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