CVE-2013-1092
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUnquoted Windows service path vulnerability in Novell ZENworks Desktop Management 7-7.1 where the service executables ZenRem32.exe and wm.exe are launched via unquoted paths containing spaces. Local attackers can place a malicious executable in the C:\ root directory with a name matching the first component of the unquoted path, causing it to execute with SYSTEM privileges when the service attempts to launch.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7= 7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Zenworks Desktop Management installation and versionCheck the Windows registry under HKLM\SOFTWARE\Novell\ZENworks\DesktopManagement or look for the product in Add/Remove Programs to verify version 7 or 7.1 is installedAffected if Zenworks Desktop Management version 7 or 7.1 is installed on the system
-
Check ZenRem32.exe service configurationOpen Services console (services.msc), locate any service using ZenRem32.exe, then check the service binary path in the registry at HKLM\SYSTEM\CurrentControlSet\Services\<ServiceName>\ImagePath. Also run 'sc qc <servicename>' from command promptAffected if The ImagePath value contains spaces and is not enclosed in quotation marks
-
Check wm.exe service configurationOpen Services console (services.msc), locate any service using wm.exe, then check the service binary path in the registry at HKLM\SYSTEM\CurrentControlSet\Services\<ServiceName>\ImagePath. Also run 'sc qc <servicename>' from command promptAffected if The ImagePath value contains spaces and is not enclosed in quotation marks
-
Inspect root directory for suspicious executablesList files in C:\ directory using 'dir C:\' or File Explorer to see if any executable files with names matching the first component of any unquoted service path exist (e.g., 'Program.exe' if path is C:\Program Files\...)Affected if An executable exists in C:\ whose name matches the first word before a space in an unquoted service path
A system is affected if Zenworks Desktop Management 7 or 7.1 is installed AND either the ZenRem32.exe or wm.exe service has an unquoted path containing spaces, allowing potential executable placement in C:\ that could be hijacked.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataEither remove or rename the vulnerable executables if unused, upgrade to a patched version if available, or manually add quotes around the service binary paths in the Windows registry for the affected services.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1092 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-1092 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data