CVE-2013-1079
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 · uneditedDirectory traversal vulnerability in the ISCreateObject method in an ActiveX control in InstallShield\ISProxy.dll in AdminStudio in Novell ZENworks Configuration Management (ZCM) 10.3 through 11.2 allows remote attackers to execute arbitrary local DLL files via a crafted web page that also calls the Initialize method.
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 confidenceDirectory traversal vulnerability in the ISCreateObject method of the InstallShield ISProxy.dll ActiveX control in Novell ZENworks Configuration Management 10.3-11.2 allows remote attackers to execute arbitrary local DLL files via a crafted web page that also calls the Initialize method.
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= 10.3= 10.3.1= 10.3.2= 10.3.3= 11= 11.1= 11.1a= 11.2CVSS 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
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Check if Novell ZENworks Configuration Management is installedLook for ZENworks installation directory. On Windows, check C:\Novell\ZENworks or %ProgramFiles%\Novell\ZENworks. On Linux, check /opt/novell/zenworks.Affected if The ZENworks installation directory exists and contains ZENworks components.
-
Verify the installed ZENworks versionCheck the version of installed ZENworks. On Windows, look for version info in the ZENworks installation directory or check registry keys under HKLM\SOFTWARE\Novell\ZENworks. On Linux, check /opt/novell/zenworks/share/version or similar version files.Affected if The installed version matches any of: 10.3, 10.3.1, 10.3.2, 10.3.3, 11, 11.1, 11.1a, or 11.2.
-
Locate the ISProxy.dll ActiveX componentSearch for ISProxy.dll file on the system. Common locations include the ZENworks installation directory, Windows\System32, or subdirectories under the ZENworks folder. Use: dir /s C:\ISProxy.dll or find / -name ISProxy.dll on Linux.Affected if The ISProxy.dll file exists on the system.
-
Check if the ActiveX control is registeredOn Windows, check registry for ISProxy.dll registration. Look in HKLM\SOFTWARE\Classes\CLSID for the ISProxy CLSID or check HKLM\SOFTWARE\Microsoft\Code Store Database\Distribution Units for ActiveX control entries.Affected if The ISProxy.dll ActiveX control is registered in the Windows registry.
-
Check browser ActiveX settings for the vulnerable controlIn Internet Explorer, check ActiveX filtering settings or examine add-on management for the ISProxy.dll component. Also check browser security zones settings that permit ActiveX controls from the ZENworks server or intranet sites.Affected if Browser settings allow the ISProxy.dll ActiveX control to run, or the control is listed as an enabled browser add-on.
A user is affected if Novell ZENworks Configuration Management version 10.3 through 11.2 is installed with the ISProxy.dll ActiveX control present and enabled in the browser.
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 dataDisable or restrict the vulnerable ActiveX control in browsers, and apply vendor patches when available. Consider removing the affected ISProxy.dll component if not required.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1079 — 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-1079 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