# CVE-2005-1590: Security feature bypass in n/a

> Local users can bypass password protection and access the administrative interface of the Altiris Client Service by manipulating hidden window settings.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** No
- **Published:** 16 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rjp9-3q7v-4mq5

## What is CVE-2005-1590?

CVE-2005-1590 is a medium-severity 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 (ACLIENT.EXE) 6.0.88 allows local users to disable password protection and access the administrative interface by finding and showing the "Altiris Client Service" hidden window, disabling the password protection, disabling the "Hide client tray icon box" option, then opening the AClient tray icon and using the View Log File option, a different vulnerability than CVE-2004-2070.

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

It affects 2 products.


Products: Altiris Client Service, Altiris Deployment Solution.

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

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

## Is CVE-2005-1590 being exploited?

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

Public exploit code:

- Altiris Deployment Solution 5.6 - Client Service Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1590 is a medium-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1590 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-2005-1590/ (Markdown: https://insights.sbomify.com/CVE-2005-1590/index.md)
```

## Sources

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

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