# CVE-2004-2070: Command injection in n/a

> Local users can execute arbitrary commands via the View Log File option in the Altiris Client Service tray icon.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-3wrg-ww99-5m6c

## What is CVE-2004-2070?

CVE-2004-2070 is a high-severity command injection vulnerability in n/a, published on 16 May 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

The Altiris Client Service for Windows 5.6 SP1 Hotfix E (5.6.181) allows local users to execute arbitrary commands by opening the AClient tray icon and using the View Log File option, a different vulnerability than CVE-2005-1590.

## Which versions are affected by CVE-2004-2070?


## How do I fix CVE-2004-2070?

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

## Is CVE-2004-2070 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2070 and fix it if it is affected.

What it is: CVE-2004-2070 is a high-severity command injection vulnerability in n/a, published on 16 May 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-2004-2070 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-2004-2070/ (Markdown: https://insights.sbomify.com/CVE-2004-2070/index.md)
```

## Sources

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

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