Advanced Malware Protection For EndpointsApplication · Cisco
CVE-2020-3314
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 file scan process of Cisco AMP for Endpoints Mac Connector Software could cause the scan engine to crash during the scan of local files, resulting in a restart of the AMP Connector and a denial of service (DoS) condition of the Cisco AMP for Endpoints service. The vulnerability is due to insufficient input validation of specific file attributes. An attacker could exploit this vulnerability by providing a crafted file to a user of an affected system. A successful exploit could allow the attacker to cause the Cisco AMP for Endpoints service to crash, resulting in missed detection and logging of the potentially malicious file. Continued attempts to scan the file could result in a DoS condition of the Cisco AMP for Endpoints 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 · moderate confidenceA denial of service vulnerability exists in Cisco AMP for Endpoints Mac Connector Software's file scanning engine. The scan engine crashes when processing files with crafted attributes due to insufficient input validation. Successful exploitation causes the AMP service to restart, resulting in missed malware detection and potential repeated DoS conditions from ongoing scan attempts.
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
< 1.12.3.738CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/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 installed Cisco AMP for Endpoints version on MacOpen a terminal and run: defaults read /Applications/Cisco\ AMP.app/Contents/Info CFBundleVersion 2>/dev/null || grep -r 'CFBundleVersion' /Applications/Cisco\ AMP.app/Contents/Info.plist 2>/dev/nullAffected if The displayed version number is less than 1.12.3.738 (for example, 1.12.3.737 or earlier)
-
Verify the AMP service is runningRun the command: ps aux | grep -i 'Cisco AMP' or check System Preferences > Users & Groups > Login Items for Cisco AMPAffected if The Cisco AMP service appears in the process list and is actively running
-
Confirm file scanning engine is enabledOpen Cisco AMP GUI and navigate to Settings > Scanning, or check the configuration file at ~/Library/Application\ Support/Cisco/AMP/conf/amp.confAffected if Real-time file scanning or on-demand scanning is turned on (this is the default and required state for the vulnerability to apply)
-
Look for AMP service crash or restart eventsCheck Console.app for crash reports containing 'Cisco AMP' or 'ampdaemon', or run: log show --predicate 'process == "ampdaemon"' --last 24h | grep -i crashAffected if Recent crash logs or unexpected service restarts are present in the logs
You are affected if the installed version is below 1.12.3.738 AND the file scanning engine is enabled on your Mac system.
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 data1.12.3.738
Apply the vendor patch from Cisco for AMP for Endpoints Mac Connector Software. Until patched, monitor for service disruptions and consider restricting user access to untrusted file sources.
Fix this in Advanced Malware Protection For Endpoints
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3314 — 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-2020-3314 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