dbcve.org
Advanced Malware Protection For EndpointsApplication · Cisco

CVE-2020-3343

MEDIUM · 5.5 CVSS v3.1 Published 2020-05-22
Fix available
A fix is available. Upgrade to after 1.12.3.738 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
A vulnerability in Cisco AMP for Endpoints Linux Connector Software and Cisco AMP for Endpoints Mac Connector Software could allow an authenticated, local attacker to cause a buffer overflow on an affected device. The vulnerability is due to insufficient input validation. An attacker could exploit this vulnerability by sending a crafted packet to an affected device. A successful exploit could allow the attacker to cause the Cisco AMP for Endpoints service to crash and restart.

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 confidence

Buffer overflow vulnerability in Cisco AMP for Endpoints Linux and Mac Connector Software due to insufficient input validation. Authenticated local attacker can send a crafted packet to cause the AMP service to crash and restart, resulting in denial of service.

MitigationApply the vendor patch from Cisco for affected versions of AMP for Endpoints Connector Software. Ensure systems are updated to a patched version.

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
Affected:<= 1.12.3.698<= 1.12.3.738

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Cisco AMP for Endpoints Connector is installed
    On Linux, check for the presence of AMP for Endpoints directories or processes (e.g., look for ampdaemon, ampagent processes, or check /opt/cisco/amp directory). On Mac, check /Applications for Cisco AMP or use 'ps aux | grep -i amp' to find running AMP processes.
    Affected if The product is not installed or no AMP-related processes are found, then not affected.
  2. Determine the installed version of AMP for Endpoints Connector
    On Linux, run the amp CLI tool if available (e.g., 'ampcli --version' or '/opt/cisco/amp/ampcli -v') or check version files in the installation directory. On Mac, right-click the Cisco AMP app in /Applications and select 'Get Info' to view version, or use 'ampcli --version' if installed.
    Affected if Unable to determine version means affected status cannot be assessed.
  3. Compare installed version against affected ranges
    The affected versions are: 1.12.3.698 and earlier; 1.12.3.738 and earlier. Compare your installed version number to these thresholds. Note that both 1.12.3.698 and 1.12.3.738 represent upper bounds, meaning versions like 1.12.3.650, 1.12.2.x, or any 1.12.0.x through 1.12.3 versions below these build numbers are vulnerable.
    Affected if Installed version is 1.12.3.698 or lower, OR 1.12.3.738 or lower (if using that build branch).
  4. Verify the AMP service is running (confirming exploitable state)
    On Linux, run 'systemctl status amp' or 'ps aux | grep amp' to check if the AMP daemon is active. On Mac, check if the AMP service is running via 'launchctl list | grep amp' or Activity Monitor.
    Affected if AMP service is running and version is in the affected range, indicating the system is vulnerable to the buffer overflow DoS.

The environment is affected if Cisco AMP for Endpoints Connector is installed with a version of 1.12.3.698 or earlier, or 1.12.3.738 or earlier, and the AMP service is active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.12.3.738
Interim mitigation

Apply the vendor patch from Cisco for affected versions of AMP for Endpoints Connector Software. Ensure systems are updated to a patched version.

Fix this in Advanced Malware Protection For Endpoints Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3343 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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