# CVE-2009-3233: Command injection in n/a

> Local attackers can execute arbitrary commands via crafted filenames in directories monitored by changetrack.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2009
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2009-3233, DSA-1891-1, GHSA-62jg-wqh5-h6g8

## What is CVE-2009-3233?

CVE-2009-3233 is a high-severity command injection vulnerability in n/a, published on 17 Sep 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

changetrack 4.3 allows local users to execute arbitrary commands via CRLF sequences and shell metacharacters in a filename in a directory that is checked by changetrack.

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

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

It affects 1 product.


Products: Cameron Morland Changetrack.

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

Apply the vendor's patch.

## Is CVE-2009-3233 being exploited?

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

Public exploit code:

- Changetrack 4.3-3 - Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-3233 is a high-severity command injection vulnerability in n/a, published on 17 Sep 2009. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-3233 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-3233/ (Markdown: https://insights.sbomify.com/CVE-2009-3233/index.md)
```

## Sources

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

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