CVE-2020-3334
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 ARP packet processing of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software for Cisco Firepower 2100 Series Security Appliances could allow an unauthenticated, adjacent attacker to cause an affected device to reload, resulting in a denial of service (DoS) condition on an affected device. The vulnerability is due to incorrect processing of ARP packets received by the management interface of an affected device. An attacker could exploit this vulnerability by sending a series of unicast ARP packets in a short timeframe that would reach the management interface of an affected device. A successful exploit could allow the attacker to consume resources on an affected device, which would prevent the device from sending internal system keepalives and eventually cause the device to reload, resulting in a denial of service (DoS) condition.
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 vulnerability in ARP packet processing on the management interface of Cisco ASA and FTD Software for Firepower 2100 Series allows an adjacent, unauthenticated attacker to send malicious unicast ARP packets that exhaust device resources, preventing internal keepalives and causing the device to reload, resulting in denial of service.
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>= 9.10, < 9.10.1.37>= 9.12, < 9.12.3>= 9.13, < 9.13.1.2< 6.6.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelRun 'show version' or check hardware inventory to confirm the device is a Firepower 2100 Series applianceAffected if Device model is Firepower 2100 Series (the only affected hardware platform)
-
Identify software typeRun 'show version' to determine if the device runs Cisco ASA Software or Cisco Firepower Threat Defense (FTD)Affected if Software is either ASA or FTD (only these products are affected)
-
Check ASA versionIf running ASA, run 'show version' and locate the running software version (e.g., 9.12.1). Compare against affected ranges: >= 9.10 but < 9.10.1.37; >= 9.12 but < 9.12.3; >= 9.13 but < 9.13.1.2Affected if ASA version falls within any of the affected version ranges
-
Check FTD versionIf running FTD, run 'show version' or check the FTD software version. Compare against affected range: < 6.6.0Affected if FTD version is below 6.6.0
-
Verify management interface statusRun 'show interface' or 'show ip address' to confirm the management interface (typically Management0/0) is configured and activeAffected if Management interface is configured and reachable (exploit requires sending ARP packets to the management interface)
The device is affected if it is a Firepower 2100 Series running ASA in versions 9.10.x before 9.10.1.37, 9.12.x before 9.12.3, or 9.13.x before 9.13.1.2; or running FTD version below 6.6.0, and the management interface is configured and accessible on a network segment.
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 data6.6.09.10.1.379.12.3
Apply the Cisco software update that corrects ARP packet handling on the management interface. If no patch is available, restrict physical/logical access to the management network segment to prevent adjacent attacks.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3334 — 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-3334 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