# CVE-2009-0693: Memory corruption in n/a

> Remote attackers can execute arbitrary code via buffer overflows in Wyse Device Manager components, requiring immediate patching.

- **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:** 16 Sep 2024
- **Also known as:** GHSA-g3qf-xr97-56vj

## What is CVE-2009-0693?

CVE-2009-0693 is a high-severity memory corruption 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

Multiple buffer overflows in Wyse Device Manager (WDM) 4.7.x allow remote attackers to execute arbitrary code via (1) the User-Agent HTTP header to hserver.dll or (2) unspecified input to hagent.exe.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Dell Wyse Device Manager.

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

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

## Is CVE-2009-0693 being exploited?

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

Public exploit code:

- Wyse - Machine Remote Power Off (Denial of Service) (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-0695](https://insights.sbomify.com/CVE-2009-0695/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0693 is a high-severity memory corruption 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: There is no known exploitation of CVE-2009-0693 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-2009-0693/ (Markdown: https://insights.sbomify.com/CVE-2009-0693/index.md)
```

## Sources

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

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