CVE-2013-0108
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 · uneditedAn ActiveX control in HscRemoteDeploy.dll in Honeywell Enterprise Buildings Integrator (EBI) R310, R400.2, R410.1, and R410.2; SymmetrE R310, R410.1, and R410.2; ComfortPoint Open Manager (aka CPO-M) Station R100; and HMIWeb Browser client packages allows remote attackers to execute arbitrary code via a crafted HTML document.
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 · moderate confidenceAn ActiveX control vulnerability in HscRemoteDeploy.dll affecting multiple Honeywell building management systems (EBI, SymmetrE, ComfortPoint Open Manager, HMIWeb Browser) allows remote code execution via malicious HTML documents. The vulnerability stems from insecure handling of ActiveX parameters enabling arbitrary code to run with the privileges of the browser process.
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= r310= r400.2= r410.1= r410.2= r310= r400.2= r410.1= r100CVSS 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.
-
Locate the vulnerable ActiveX DLLSearch for HscRemoteDeploy.dll on the system using file search or command: dir /s /b C:\HscRemoteDeploy.dll 2>nulAffected if The file HscRemoteDeploy.dll exists on the system in any directory
-
Check if the ActiveX control is registeredExamine Windows registry for the ActiveX control CLSID under HKLM\SOFTWARE\Classes\CLSID or HKCU\SOFTWARE\Classes\CLSID. Search for entries containing 'HscRemoteDeploy' or the specific CLSID associated with this control.Affected if The ActiveX control is registered in the Windows registry and can be instantiated by Internet Explorer
-
Identify installed Honeywell software versionCheck Add/Remove Programs or the program directory for Honeywell Enterprise Buildings Integrator, SymmetrE, or ComfortPoint Open Manager. Look for version information in the software itself or its installation path.Affected if The installed version matches r310, r400.2, r410.1, r410.2 for EBI/SymmetrE, or r100 for ComfortPoint Open Manager
-
Verify browser ActiveX settingsCheck Internet Explorer security settings or group policy for ActiveX controls. Examine the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\PreApproved for the control CLSID.Affected if ActiveX controls are enabled and the vulnerable control is not blocked by kill-bit settings in the registry
A system is affected if HscRemoteDeploy.dll is present, the ActiveX control is registered, and the installed Honeywell software version matches the vulnerable releases (r310, r400.2, r410.1, r410.2, or r100) with ActiveX controls 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 ActiveX controls in affected browsers, implement network segmentation to isolate building management systems, and apply vendor-supplied patches or set kill bits for the vulnerable ActiveX control.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0108 — 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-0108 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