# CVE-2006-6678: Command injection in n/a

> Attackers can execute arbitrary commands via shell metacharacters in filenames during textarea editing in Netrik.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 21 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-6678, DSA-1251-1, GHSA-37rp-7j34-hmr2

## What is CVE-2006-6678?

CVE-2006-6678 is a high-severity command injection vulnerability in n/a, published on 21 Dec 2006. 

### Official description

The edit_textarea function in form-file.c in Netrik 1.15.4 and earlier does not properly verify temporary filenames when editing textarea fields, which allows attackers to execute arbitrary commands via shell metacharacters in the filename.

## Which versions are affected by CVE-2006-6678?

It affects 1 product.


Products: Netrik Netrik.

## How do I fix CVE-2006-6678?

Apply the vendor's patch.

## Is CVE-2006-6678 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6678 and fix it if it is affected.

What it is: CVE-2006-6678 is a high-severity command injection vulnerability in n/a, published on 21 Dec 2006. 
Exploitation: There is no known exploitation of CVE-2006-6678 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-2006-6678/ (Markdown: https://insights.sbomify.com/CVE-2006-6678/index.md)
```

## Sources

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

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