CVE-2022-20866 remediation guide
Cisco Cisco Adaptive Security Appliance (ASA) Software, adaptive security appliance software, secure firewall threat defense
A vulnerability in the handling of RSA keys on devices running Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to retrieve an RSA private key. This vulnerability is due to a logic error when the RSA key is stored in memory on a hardware platform that performs hardware-based cryptography. An attacker could exploit this vulnerability by using a Lenstra side-channel attack against the targeted device. A successful exploit could allow the attacker to retrieve the RSA private key. The following con...
Identify the affected asset
Confirm whether Cisco Cisco Adaptive Security Appliance (ASA) Software, adaptive security appliance software, secure firewall threat defense is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= 9.16.0 < 9.16.3.19, >= 9.17.0 < 9.17.1.13, >= 9.18.0 < 9.18.2, >= 7.0.0 < 7.0.4, >= 7.1.0 < 7.2.0.1. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
FIRST EPSS indicates an elevated probability of exploitation. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: 9.16.3.19, 9.17.1.13, 9.18.2, 7.0.4, 7.2.0.1. Preserve configuration and rollback material before change.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.