Advanced Malware Protection For EndpointsApplication · Cisco

CVE-2020-3350

MEDIUM · 6.3 CVSS v3.1 Published 2020-06-18
Fix available
A fix is available. Upgrade to 0.102.4 / 1.12.4 or later.
See remediation →
65/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 the endpoint software of Cisco AMP for Endpoints and Clam AntiVirus could allow an authenticated, local attacker to cause the running software to delete arbitrary files on the system. The vulnerability is due to a race condition that could occur when scanning malicious files. An attacker with local shell access could exploit this vulnerability by executing a script that could trigger the race condition. A successful exploit could allow the attacker to delete arbitrary files on the system that the attacker would not normally have privileges to delete, producing system instability or causing the endpoint software to stop working.

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

A race condition vulnerability in Cisco AMP for Endpoints and Clam AntiVirus allows an authenticated local attacker with shell access to delete arbitrary files on the system by triggering the race during malicious file scanning.

MitigationApply vendor security updates/patches from Cisco for AMP for Endpoints and ensure ClamAV is updated to the latest version to remediate the race condition.

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.4
Clam AntivirusApplication
Affected:< 0.102.4
FedoraOperating system
Affected:= 31= 32
Debian LinuxOperating system
Affected:= 9.0
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 16.04= 18.04= 20.04

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

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

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

  1. Check Cisco AMP for Endpoints version
    Identify if Cisco AMP for Endpoints is installed and retrieve its version number using system package management tools or the AMP-specific diagnostic command
    Affected if The installed version is below 1.12.4
  2. Check ClamAV version
    Run 'clamd --version' or check the installed clamd package version using the system package manager
    Affected if The installed ClamAV version is below 0.102.4
  3. Determine if file scanning service is active
    Check if the ClamAV daemon (clamd) or AMP connector service is running and configured to scan files on access
    Affected if The scanning service is enabled and actively processing files, which is required to trigger the race condition
  4. Verify local shell access exposure
    Assess whether untrusted local users have shell access to the system, as the vulnerability requires authenticated local attacker access
    Affected if Untrusted local users have shell access to the affected system

You are affected if either Cisco AMP for Endpoints is installed below version 1.12.4 or ClamAV is installed below version 0.102.4, and the file scanning service is active with untrusted local users having shell access.

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 0.102.4 / 1.12.4 or later
Fixed in 0.102.41.12.4
Interim mitigation

Apply vendor security updates/patches from Cisco for AMP for Endpoints and ensure ClamAV is updated to the latest version to remediate the race condition.

Fix this in Advanced Malware Protection For Endpoints Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3350 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-3350 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