# CVE-2010-0111: Command injection in n/a

> Remote attackers can execute arbitrary programs on Symantec AntiVirus servers by sending a malicious UNC path to the Intel Alert Handler service.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jan 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c8p5-6xf7-qcx4

## What is CVE-2010-0111?

CVE-2010-0111 is a critical command injection vulnerability in n/a, published on 31 Jan 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HDNLRSVC.EXE in the Intel Alert Handler service (aka Symantec Intel Handler service) in Intel Alert Management System (aka AMS or AMS2), as used in Symantec AntiVirus Corporate Edition (SAVCE) 10.x before 10.1 MR10, Symantec System Center (SSC) 10.x, and Symantec Quarantine Server 3.5 and 3.6, allows remote attackers to execute arbitrary programs by sending msgsys.exe a UNC share pathname, which is used directly in a CreateProcessA (aka CreateProcess) call.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2010-0111?

It affects 3 products.


Products: Symantec Antivirus, Symantec Antivirus Central Quarantine Server, Symantec System Center.

## How do I fix CVE-2010-0111?

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

## Is CVE-2010-0111 being exploited?

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

Public exploit code:

- Symantec System Center Alert Management System (hndlrsvc.exe) Arbitrary Command Execution (metasploit)

## Other vulnerabilities in n/a

- [CVE-2010-0108](https://insights.sbomify.com/CVE-2010-0108/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1429](https://insights.sbomify.com/CVE-2009-1429/): Command injection in n/a (critical 10.0)
- [CVE-2012-4953](https://insights.sbomify.com/CVE-2012-4953/): Memory corruption in n/a (critical 9.3)
- [CVE-2011-0688](https://insights.sbomify.com/CVE-2011-0688/): Command injection in n/a (critical 9.3)
- [CVE-2009-1430](https://insights.sbomify.com/CVE-2009-1430/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0111 and fix it if it is affected.

What it is: CVE-2010-0111 is a critical command injection vulnerability in n/a, published on 31 Jan 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-0111 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-2010-0111/ (Markdown: https://insights.sbomify.com/CVE-2010-0111/index.md)
```

## Sources

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

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