CVE-2020-3298
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 of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause the reload of an affected device, resulting in a denial of service (DoS) condition. The vulnerability is due to improper memory protection mechanisms while processing certain OSPF packets. An attacker could exploit this vulnerability by sending a series of malformed OSPF packets in a short period of time to an affected device. A successful exploit could allow the attacker to cause a reload of the affected device, resulting in a DoS condition for client traffic that is traversing the device.
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 confidenceMemory corruption vulnerability in Cisco ASA and FTD OSPF packet processing. Improper memory protection during handling of malformed OSPF packets allows an unauthenticated remote attacker to trigger device reload, causing 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>= 6.2.0, < 6.2.3.16>= 6.3.0, < 6.3.0.6>= 6.4.0, < 6.4.0.9>= 6.5.0, < 6.5.0.5>= 9.6.0, <= 9.6.4.40>= 9.8.0, <= 9.8.4.17>= 9.9.0, <= 9.9.2.66>= 9.10.0, <= 9.10.1.37>= 9.12.0, <= 9.12.3.7>= 9.13.0, <= 9.13.1.7CVSS 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 device type and software platformLog into the device CLI and run 'show version' to determine if the device is running Cisco ASA Software or Cisco Firepower Threat Defense (FTD)Affected if The device runs ASA or FTD software - this vulnerability only affects these platforms
-
Check the installed software versionOn ASA, run 'show version | include Version'. On FTD, run 'show version' or check via Firepower Management Center. Record the full version number (e.g., 9.8.4.17, 6.4.0.8)Affected if The version falls within any of the affected ranges: ASA 9.6.0-9.6.4.40, 9.8.0-9.8.4.17, 9.9.0-9.9.2.66, 9.10.0-9.10.1.37, 9.12.0-9.12.3.7, 9.13.0-9.13.1.7 OR FTD 6.2.0-6.2.3.15, 6.3.0-6.3.0.5, 6.4.0-6.4.0.8, 6.5.0-6.5.0.4
-
Verify OSPF is enabled and configuredRun 'show ospf' or 'show running-config | include ospf' on ASA. On FTD, check OSPF configuration via 'show ospf' or through Firepower Management Center under Device > RoutingAffected if OSPF process is configured and active on the device - the vulnerability is triggered by processing malformed OSPF packets, so OSPF must be running for exploitation
-
Confirm OSPF neighbor relationships existRun 'show ospf neighbor' to list active OSPF neighbors. Also check 'show ospf interface' to see which interfaces have OSPF enabledAffected if There are active OSPF neighbors or OSPF is advertised on any interface - this indicates the device is actively processing OSPF traffic that could contain malformed packets
The device is affected if it runs vulnerable ASA or FTD software versions AND has OSPF protocol enabled and configured, regardless of whether OSPF neighbors are currently established.
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.2.3.166.3.0.66.4.0.9
Apply Cisco security updates for ASA and FTD software. As a compensating control, restrict OSPF peering to trusted neighbors at network edge if software update is not immediately feasible.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3298 — 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-3298 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