CVE-2010-0111
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 · uneditedHDNLRSVC.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.
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 confidenceThe Intel Alert Handler service (HDNLRSVC.EXE) in Symantec Alert Management System accepts a UNC share pathname from remote attackers and passes it directly to CreateProcessA without validation, allowing arbitrary code execution.
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.0= 10.0.1= 10.0.1.1= 10.0.1.2= 10.0.2= 10.0.2.1= 10.0.2.2= 10.0.3= 10.0.4= 10.0.5= 10.0.6= 10.0.7= 10.0= 10.1= 3.5= 3.6CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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.
-
Verify Intel Alert Handler service is installedOpen Windows Services console (services.msc) and look for 'Intel Alert Handler' service, or check for HDNLRSVC.EXE process in Task ManagerAffected if The service or process named 'Intel Alert Handler' or HDNLRSVC.EXE is present on the system
-
Check installed Symantec Antivirus versionOpen Windows Control Panel, go to Add/Remove Programs (or Programs and Features), locate 'Symantec AntiVirus' or 'Symantec Antivirus Corporate Edition' and note the version numberAffected if The installed version matches 10.0, 10.0.1, 10.0.1.1, 10.0.1.2, 10.0.2, 10.0.2.1, 10.0.2.2, 10.0.3, 10.0.4, 10.0.5, 10.0.6, or 10.0.7
-
Check installed Symantec System Center versionOpen Add/Remove Programs and locate 'Symantec System Center', note the version numberAffected if The installed version is 10.0 or 10.1
-
Check installed Central Quarantine Server versionOpen Add/Remove Programs and locate 'Symantec Antivirus Central Quarantine Server', note the version numberAffected if The installed version is 3.5 or 3.6
-
Verify network exposure of the Alert Handler serviceUse command 'netstat -an' or a network port scanner to check if port 5000 (default Intel Alert Handler port) or related ports are listening on network interfacesAffected if The Intel Alert Handler service is listening on a reachable network port (not localhost only)
-
Confirm vulnerable service executable existsCheck for the presence of HDNLRSVC.EXE in the Symantec installation directory (typically in C:\Program Files\Symantec\ or C:\Program Files\Symantec AntiVirus\)Affected if HDNLRSVC.EXE exists in the Symantec program directory
The system is affected if Intel Alert Handler service (HDNLRSVC.EXE) is running AND the installed product version matches one of the listed vulnerable versions AND the service is network-accessible.
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.
dbcve · scopedApply vendor patch (Symantec AntiVirus Corporate Edition 10.1 MR10 or later, or upgrade to supported versions). If immediate patching is not feasible, restrict network access to the Intel Alert Handler service.
Symantec AntiVirus Corporate Edition 10.1 MR10 or later; Symantec System Center 10.1 or later; Symantec Quarantine Server 3.6.1 or later
- 1. Identify all affected systems running Symantec AntiVirus Corporate Edition 10.x, Symantec System Center 10.x, or Symantec Quarantine Server 3.5/3.6
- 2. Verify current installed versions on each affected system
- 3. Contact Symantec support or visit the official security advisory page to obtain the patched version (10.1 MR10 or later)
- 4. Download the appropriate patch or upgrade package for your specific product version
- 5. Test the patch in a non-production environment before deploying
- 6. Apply the patch/upgrade to production systems following standard change management procedures
- 7. Verify the update was successfully applied and the service is running correctly
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2010-0111 — 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-2010-0111 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