CVE-2021-1386
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 · uneditedA vulnerability in the dynamic link library (DLL) loading mechanism in Cisco Advanced Malware Protection (AMP) for Endpoints Windows Connector, ClamAV for Windows, and Immunet could allow an authenticated, local attacker to perform a DLL hijacking attack on an affected Windows system. To exploit this vulnerability, the attacker would need valid credentials on the system. The vulnerability is due to insufficient validation of directory search paths at run time. An attacker could exploit this vulnerability by placing a malicious DLL file on an affected system. A successful exploit could allow the attacker to execute arbitrary code with SYSTEM privileges.
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 confidenceA DLL hijacking vulnerability in Cisco AMP for Endpoints Windows Connector, ClamAV for Windows, and Immunet allows an authenticated local attacker to place a malicious DLL file that gets loaded by the vulnerable application due to insufficient validation of directory search paths at runtime, achieving arbitrary code execution with SYSTEM privileges.
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< 7.3.15< 0.103.2< 7.4.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Cisco AMP for Endpoints Windows Connector is installedOpen Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check for presence of folder C:\Program Files\Cisco\AMP (or equivalent). Use command: dir /s /b "C:\Program Files\Cisco\AMP" 2>nulAffected if The product is installed AND its version is below 7.3.15
-
Check if Cisco ClamAV for Windows is installedCheck for presence of ClamAV installation directory (commonly C:\Program Files\ClamAV or C:\Program Files (x86)\ClamAV). Use command: dir /s /b "C:\Program Files\ClamAV" 2>nul OR dir /s /b "C:\Program Files (x86)\ClamAV" 2>nulAffected if The product is installed AND its version is below 0.103.2
-
Check if Cisco Immunet is installedCheck for presence of Immunet installation directory (commonly C:\Program Files\Immunet). Use command: dir /s /b "C:\Program Files\Immunet" 2>nulAffected if The product is installed AND its version is below 7.4.0
-
Determine installed version of Cisco AMPCheck the version of amp.exe or look in Windows Registry under the uninstall key for Cisco AMP, or run: wmic product where "name like 'Cisco AMP%'" get versionAffected if Version returned is blank, not found, or less than 7.3.15
-
Determine installed version of ClamAVRun clamscan --version or check the version information ofclamd.exe or freshclam.exe in the installation directoryAffected if Version returned is less than 0.103.2 or command fails to execute
-
Determine installed version of ImmunetCheck the version of protect.exe in the Immunet installation directory, or look in Windows Registry under the uninstall key for ImmunetAffected if Version returned is less than 7.4.0 or command fails to execute
A user is affected if any of these three Cisco products (AMP for Endpoints, ClamAV for Windows, or Immunet) is installed with a version below the respective threshold (7.3.15, 0.103.2, or 7.4.0), making them vulnerable to DLL hijacking with SYSTEM privilege escalation.
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 data0.103.27.3.157.4.0
Apply vendor patches from Cisco for the affected products; until patched, restrict local access to trusted personnel only and monitor for suspicious DLL files in application directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1386 — 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-2021-1386 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