Advanced Malware Protection For EndpointsApplication · Cisco
CVE-2019-1932
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 Cisco Advanced Malware Protection (AMP) for Endpoints for Windows could allow an authenticated, local attacker with administrator privileges to execute arbitrary code. The vulnerability is due to insufficient validation of dynamically loaded modules. An attacker could exploit this vulnerability by placing a file in a specific location in the Windows filesystem. A successful exploit could allow the attacker to execute the code with the privileges of the AMP service.
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 local privilege escalation vulnerability in Cisco AMP for Endpoints for Windows allows an authenticated administrator to place a malicious file in a specific Windows filesystem location. Due to insufficient validation of dynamically loaded modules, the AMP service loads and executes this malicious code with elevated service privileges, achieving local privilege escalation from administrator to SYSTEM-level 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
Advanced Malware Protection For EndpointsApplication
= 6.2\(3\)CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:H/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.
-
Confirm Cisco AMP for Endpoints is installedOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Cisco AMP*"}' in PowerShellAffected if The product is listed as installed on the system
-
Identify installed versionOpen Windows Control Panel > Programs and Features, locate 'Cisco Advanced Malware Protection' or 'Cisco AMP for Endpoints', and note the version column; alternatively, check the AMP client UI About sectionAffected if The installed version is exactly 6.2.3 (or falls within the 6.2.3 release line)
-
Inspect AMP service configurationOpen Services.msc, locate the 'Cisco AMP for Endpoints' service, right-click and select Properties, verify the service is running and note the executable pathAffected if The AMP service is running with elevated privileges and loads external modules from a configurable path
-
Identify vulnerable module loading pathExamine the AMP service executable directory (typically C:\Program Files\Cisco\AMP\ or similar location in Program Files) for subdirectories used for plugin/module loading; review any configuration files in the AMP installation directory that specify module pathsAffected if The AMP installation directory contains writable locations where untrusted modules could be placed and loaded by the service
A system is affected if Cisco AMP for Endpoints version 6.2.3 is installed and the AMP service can load modules from a filesystem location accessible to an authenticated administrator.
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 dataApply the vendor patch from Cisco when available. Until then, restrict physical and console access to systems running AMP to trusted administrators only, and monitor for unauthorized file placement in the specific filesystem location used by the vulnerable module loading mechanism.
Fix this in Advanced Malware Protection For Endpoints
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1932 — 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-2019-1932 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