# CVE-2005-2368: Command injection in n/a

> Attackers can execute arbitrary commands via malicious fold expressions in Vim when modelines are enabled, 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:** 26 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2368, DTSA-12-1, GHSA-w427-f3fp-6x6x, RHSA-2005:745

## What is CVE-2005-2368?

CVE-2005-2368 is a critical command injection vulnerability in n/a, published on 26 Jul 2005. 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

vim 6.3 before 6.3.082, with modelines enabled, allows external user-assisted attackers to execute arbitrary commands via shell metacharacters in the (1) glob or (2) expand commands of a foldexpr expression for calculating fold levels.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vim` | Red Hat:enterprise_linux:3::as | All versions | 1:6.3.046-0.30E.4 |
| `vim-X11` | Red Hat:enterprise_linux:3::as | All versions | 1:6.3.046-0.30E.4 |
| `vim-common` | Red Hat:enterprise_linux:3::as | All versions | 1:6.3.046-0.30E.4 |
| `vim-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 1:6.3.046-0.30E.4 |
| `vim-enhanced` | Red Hat:enterprise_linux:3::as | All versions | 1:6.3.046-0.30E.4 |
| `vim-minimal` | Red Hat:enterprise_linux:3::as | All versions | 1:6.3.046-0.30E.4 |
| `vim` | Red Hat:enterprise_linux:3::desktop | All versions | 1:6.3.046-0.30E.4 |
| `vim-X11` | Red Hat:enterprise_linux:3::desktop | All versions | 1:6.3.046-0.30E.4 |
| `vim-common` | Red Hat:enterprise_linux:3::desktop | All versions | 1:6.3.046-0.30E.4 |
| `vim-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 1:6.3.046-0.30E.4 |
| `vim-enhanced` | Red Hat:enterprise_linux:3::desktop | All versions | 1:6.3.046-0.30E.4 |
| `vim-minimal` | Red Hat:enterprise_linux:3::desktop | All versions | 1:6.3.046-0.30E.4 |
| `vim` | Red Hat:enterprise_linux:3::es | All versions | 1:6.3.046-0.30E.4 |
| `vim-X11` | Red Hat:enterprise_linux:3::es | All versions | 1:6.3.046-0.30E.4 |
| `vim-common` | Red Hat:enterprise_linux:3::es | All versions | 1:6.3.046-0.30E.4 |
| `vim-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 1:6.3.046-0.30E.4 |
| `vim-enhanced` | Red Hat:enterprise_linux:3::es | All versions | 1:6.3.046-0.30E.4 |
| `vim-minimal` | Red Hat:enterprise_linux:3::es | All versions | 1:6.3.046-0.30E.4 |
| `vim` | Red Hat:enterprise_linux:3::ws | All versions | 1:6.3.046-0.30E.4 |
| `vim-X11` | Red Hat:enterprise_linux:3::ws | All versions | 1:6.3.046-0.30E.4 |
| `vim-common` | Red Hat:enterprise_linux:3::ws | All versions | 1:6.3.046-0.30E.4 |
| `vim-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 1:6.3.046-0.30E.4 |
| `vim-enhanced` | Red Hat:enterprise_linux:3::ws | All versions | 1:6.3.046-0.30E.4 |
| `vim-minimal` | Red Hat:enterprise_linux:3::ws | All versions | 1:6.3.046-0.30E.4 |
| `vim` | Red Hat:enterprise_linux:4::as | All versions | 1:6.3.046-0.40E.7 |
| `vim-X11` | Red Hat:enterprise_linux:4::as | All versions | 1:6.3.046-0.40E.7 |
| `vim-common` | Red Hat:enterprise_linux:4::as | All versions | 1:6.3.046-0.40E.7 |
| `vim-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 1:6.3.046-0.40E.7 |
| `vim-enhanced` | Red Hat:enterprise_linux:4::as | All versions | 1:6.3.046-0.40E.7 |
| `vim-minimal` | Red Hat:enterprise_linux:4::as | All versions | 1:6.3.046-0.40E.7 |
| `vim` | Red Hat:enterprise_linux:4::desktop | All versions | 1:6.3.046-0.40E.7 |
| `vim-X11` | Red Hat:enterprise_linux:4::desktop | All versions | 1:6.3.046-0.40E.7 |
| `vim-common` | Red Hat:enterprise_linux:4::desktop | All versions | 1:6.3.046-0.40E.7 |
| `vim-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 1:6.3.046-0.40E.7 |
| `vim-enhanced` | Red Hat:enterprise_linux:4::desktop | All versions | 1:6.3.046-0.40E.7 |
| `vim-minimal` | Red Hat:enterprise_linux:4::desktop | All versions | 1:6.3.046-0.40E.7 |
| `vim` | Red Hat:enterprise_linux:4::es | All versions | 1:6.3.046-0.40E.7 |
| `vim-X11` | Red Hat:enterprise_linux:4::es | All versions | 1:6.3.046-0.40E.7 |
| `vim-common` | Red Hat:enterprise_linux:4::es | All versions | 1:6.3.046-0.40E.7 |
| `vim-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 1:6.3.046-0.40E.7 |

Products: Vim Development Group Vim.

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

Upgrade to a fixed version.

## Is CVE-2005-2368 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2438](https://insights.sbomify.com/CVE-2007-2438/): Code injection in n/a (high 7.6)
- [CVE-2004-1138](https://insights.sbomify.com/CVE-2004-1138/): Code injection in n/a (high 7.2)
- [CVE-2007-2953](https://insights.sbomify.com/CVE-2007-2953/): Code injection in n/a (medium 6.8)
- [CVE-2001-0408](https://insights.sbomify.com/CVE-2001-0408/): Code injection in n/a (medium 5.1)
- [CVE-2005-0069](https://insights.sbomify.com/CVE-2005-0069/): Path traversal in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-2368 is a critical command injection vulnerability in n/a, published on 26 Jul 2005. 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-2005-2368 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-2368/ (Markdown: https://insights.sbomify.com/CVE-2005-2368/index.md)
```

## Sources

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

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