CVE intelligence and bounded remediation

CVE-2026-20022 — Cisco Adaptive Security Appliance Software security vulnerability

Medium CVSS 6.5

A vulnerability in the OSPF protocol of Cisco Secure Firewall ASA Software and Cisco Secure FTD Software could allow an unauthenticated, adjacent attacker to cause an affected device to reload unexpectedly, resulting in a DoS condition when OSPF canonicalization debug is enabled by using the command debug ip ospf canon. This vulnerability is due to insufficient input validation when processing OSPF LSU packets. An attacker could exploit this vulnerability by sending crafted unauthenticated OSPF packets. A successful exploit could allow the attacker to write to memory outside of the packet data, causing the device to reload, resulting in a DoS condition.

Severity
Medium
CVSS
6.5 (3.1)
Published
2026-03-04
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-823

Affected products

  • cisco / adaptive_security_appliance_software / 9.12.1
  • cisco / adaptive_security_appliance_software / 9.12.1.2
  • cisco / adaptive_security_appliance_software / 9.12.1.3
  • cisco / adaptive_security_appliance_software / 9.12.2
  • cisco / adaptive_security_appliance_software / 9.12.2.1
  • cisco / adaptive_security_appliance_software / 9.12.2.4

Showing 6 representative product identities from 239 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Buffer bounds, memory safety, and memory corruption

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Identify affected native-code versions, build flags, architectures, parsers, codecs, drivers, and input paths in all shipped artifacts.
  • Determine whether untrusted data reaches the affected routine and the process privilege, sandbox, and network exposure.
  • Confirm statically linked, vendored, firmware, and platform-provided copies, not only package-manager records.

Remediate safely

  • Apply the maintained upstream correction or replace the affected component, then rebuild every dependent artifact from clean inputs.
  • Adopt bounds-checked interfaces, validated sizes and integer conversions, clear ownership, and memory-safe components where practical.
  • Enable supported compiler and runtime hardening and add sanitized tests and fuzz regression seeds derived from non-weaponized fixtures.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.