# CVE-2013-1092: Privilege escalation in n/a

> Local attackers can gain privileges by placing a malicious executable in the C: drive due to unquoted search paths in Novell ZENworks Desktop Management.

- **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:** Not needed
- **Fix available:** No
- **Published:** 5 May 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-j337-hcvc-rc4g

## What is CVE-2013-1092?

CVE-2013-1092 is a high-severity vulnerability in n/a, published on 5 May 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple unquoted Windows search path vulnerabilities in Novell ZENworks Desktop Management (ZDM) 7 through 7.1 might allow local users to gain privileges via a Trojan horse "program" file in the C: folder, related to an attempted launch of (1) ZenRem32.exe or (2) wm.exe.

## Which versions are affected by CVE-2013-1092?

It affects 1 product.


Products: Novell Zenworks Desktop Management.

## How do I fix CVE-2013-1092?

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

## Is CVE-2013-1092 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5073](https://insights.sbomify.com/CVE-2008-5073/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1092 and fix it if it is affected.

What it is: CVE-2013-1092 is a high-severity vulnerability in n/a, published on 5 May 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-1092 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-2013-1092/ (Markdown: https://insights.sbomify.com/CVE-2013-1092/index.md)
```

## Sources

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

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