# CVE-2009-0695: Auth bypass in n/a

> Remote attackers can bypass authentication in Wyse Device Manager to gain management access and trigger actions like power-off.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-m3cg-wrvh-hrx5

## What is CVE-2009-0695?

CVE-2009-0695 is a high-severity authentication bypass vulnerability in n/a, published on 19 Jun 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

hagent.exe in Wyse Device Manager (WDM) 4.7.x does not require authentication for commands, which allows remote attackers to obtain management access via a crafted query, as demonstrated by a V52 query that triggers a power-off action.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Dell Wyse Device Manager.

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

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

## Is CVE-2009-0695 being exploited?

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

Public exploit code:

- Wyse Rapport Hagent Fake Hserver - Command Execution (Metasploit) (exploitdb)
- Wyse Rapport Hagent Fake Hserver Command Execution (metasploit)
- Wyse - Machine Remote Power Off (Denial of Service) (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-0693](https://insights.sbomify.com/CVE-2009-0693/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0695 is a high-severity authentication bypass vulnerability in n/a, published on 19 Jun 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0695 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-0695/ (Markdown: https://insights.sbomify.com/CVE-2009-0695/index.md)
```

## Sources

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

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