CVE-2020-3195
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 Open Shortest Path First (OSPF) implementation in Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause a memory leak on an affected device. The vulnerability is due to incorrect processing of certain OSPF packets. An attacker could exploit this vulnerability by sending a series of crafted OSPF packets to be processed by an affected device. A successful exploit could allow the attacker to continuously consume memory on an affected device and eventually cause it 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 memory leak vulnerability in the OSPF routing protocol implementation in Cisco ASA and FTD Software allows remote attackers to continuously consume memory by sending specially crafted OSPF packets to affected devices, eventually causing memory exhaustion and device reload.
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>= 6.4.0, < 6.4.0.9>= 6.5.0, < 6.5.0.5= 9.12\(2\)= 9.12\(2\)= 9.12\(2\)= 9.12\(2\)= 9.12\(2\)= 9.12\(2\)= 9.12\(2\)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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Cisco device model and software versionRun 'show version' on the ASA or FTD device CLI to obtain the exact model number and running software version (for ASA use 'show version', for FTD use 'show version' or 'show running-config | include version')Affected if The software version falls within 6.4.0 through 6.4.0.8, or 6.5.0 through 6.5.0.4 for FTD; or is exactly 9.12(2) for ASA models 5505, 5510, 5512X, 5515X, 5520, 5525X, or 5540
-
Confirm OSPF routing is enabledRun 'show ospf interface' or 'show running-config ospf' to verify OSPF process is configured and running on the deviceAffected if OSPF is enabled and an OSPF process is actively running on one or more interfaces
-
Verify OSPF neighbor adjacencies existRun 'show ospf neighbor' to list all OSPF neighbors that have formed adjacencies with this deviceAffected if One or more OSPF neighbors are present, indicating the device is actively processing OSPF packets from other routers
-
Check OSPF authentication configurationRun 'show ospf interface' and examine the authentication settings for each OSPF-enabled interface to determine if MD5 authentication is configuredAffected if OSPF interfaces show no authentication configured (blank or 'disabled'), leaving the device vulnerable to unauthenticated OSPF packets
The device is affected if it runs an affected ASA or FTD version, has OSPF enabled and actively processing packets from neighbors without MD5 authentication protection.
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.4.0.96.5.0.5
Apply the Cisco security update for CVE-2020-3195 to affected ASA and FTD devices. As a workaround, implement OSPF MD5 authentication to limit packet processing to trusted neighbors and/or use route filtering to reduce attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3195 — 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-3195 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