# CVE-2013-0108: Code injection in n/a

> Remote attackers can execute arbitrary code via a crafted HTML document exploiting an ActiveX control in Honeywell building management software.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Feb 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-gqjf-wvw9-g6pm

## What is CVE-2013-0108?

CVE-2013-0108 is a medium-severity code injection vulnerability in n/a, published on 24 Feb 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 3 products.


Products: Honeywell Comfortpoint Open Manager Station, Honeywell Enterprise Buildings Integrator, Honeywell Symmetre.

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

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

## Is CVE-2013-0108 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-0108 exists.

Public exploit code:

- Honeywell HSC Remote Deployer ActiveX Remote Code Execution (metasploit)
- Honeywell HSC Remote Deployer - ActiveX Remote Code Execution (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0108 is a medium-severity code injection vulnerability in n/a, published on 24 Feb 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-0108 exists.

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-0108/ (Markdown: https://insights.sbomify.com/CVE-2013-0108/index.md)
```

## Sources

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

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