CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H/E:X/RL:X/RC:X
-
A vulnerability in the TLS cryptography functionality of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause the device to reload unexpectedly, resulting in a denial of service (DoS) condition.
This vulnerability is due to improper data validation during the TLS 1.3 handshake. An attacker could exploit this vulnerability by sending a crafted TLS 1.3 packet to an affected system through a TLS 1.3-enabled listening socket. A successful exploit could allow the attacker to cause the device to reload, resulting in a DoS condition.
Note: This vulnerability can also impact the integrity of a device by causing VPN HostScan communication failures or file transfer failures when Cisco ASA Software is upgraded using Cisco Adaptive Security Device Manager (ASDM).
Cisco has released software updates that address this vulnerability. There are workarounds that address this vulnerability.
This advisory is available at the following link:
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asa-tls-CWY6zXBThis advisory is part of the October 2024 release of the Cisco ASA, FMC, and FTD Software Security Advisory Bundled Publication. For a complete list of the advisories and links to them, see Cisco Event Response: October 2024 Semiannual Cisco ASA, FMC, and FTD Software Security Advisory Bundled Publication.
-
Vulnerable Products
This vulnerability affects Cisco ASA Software and FTD Software if they are running on a device that has an SSL listening socket and that is configured to allow the TLS 1.3 protocol.
For information about which Cisco software releases are vulnerable, see the Fixed Software section of this advisory.
Determine Whether a Device Can Process TLS Packets
To determine whether a device that is running Cisco ASA Software or FTD Software can process TLS packets, use the show asp table socket | include SSL command and look for an SSL listening socket on any TCP port. The following example shows the output for a Cisco ASA device with SSL listening sockets on TCP ports 443 and 8443:
ciscoasa# show asp table socket | include SSL
SSL 00185038 LISTEN 172.16.0.250:443 0.0.0.0:*
SSL 00188638 LISTEN 10.0.0.250:8443 0.0.0.0:*In the following table, the left column lists software features that use TLS for communication. The right column indicates the basic configuration for each feature from the show running-config CLI command. These features could cause the SSL listening sockets to be enabled.
Software Feature Possible Vulnerable Configuration HTTP server enabled1,2 http server enable
httpSSL VPN3 webvpn
enable1. The management web server is affected by this vulnerability only if it is accessed from an IP address that is in the configured http command range.2. For Cisco FTD Software, the HTTP feature is enabled from Devices > Platform Settings > HTTP Access in the Cisco Secure Firewall Management Center (FMC), formerly Firepower Management Center, console.3. For Cisco FTD Software, remote access VPN features are enabled from Devices > VPN > Remote Access in Cisco FMC Software or from Remote Access VPN in Cisco Firepower Device Manager (FDM).Identify TLS Versions in Software Configuration
To determine whether a device that is running Cisco ASA Software or FTD Software has TLS 1.3 available for connections, use the show running-config all ssl CLI command to view the minimum and maximum TLS versions, as shown in the following example:
ciscoasa> enable
ciscoasa# show running-config all ssl
ssl server-version tlsv1.2 dtlsv1.2
ssl client-version tlsv1.2
ssl server-max-version tlsv1.3
.
.
.If present, the ssl server-version configuration determines the minimum TLS protocol version the device will use during negotiation. In the preceding example, tlsv1.2 is set as the minimum TLS version.
If present, the ssl server-max-version configuration determines the highest TLS protocol version that the device will use during negotiation. In the preceding example, the device will accept TLS protocol versions up to tlsv1.3. As a result, the device is affected by this vulnerability.
If the ssl server-max-version command is absent from the output, the highest available TLS version is negotiable between the client and the device, and the device is affected by this vulnerability.
Note: If the ssl server-max-version is lower than tlsv1.3, the device is not affected by this vulnerability, and the workaround may not be necessary or may already be applied.
Products Confirmed Not Vulnerable
Only products listed in the Vulnerable Products section of this advisory are known to be affected by this vulnerability.
Cisco has confirmed that this vulnerability does not affect Cisco FMC Software.
-
If an affected device is running a Cisco ASA Software or FTD Software release that supports the ssl server-max-version command, administrators may disable TLS 1.3 as a workaround for this vulnerability.
Note: The ssl server-max-version CLI command is supported as of Cisco ASA Software releases 9.19.1.24 and 9.20.2 and Cisco FTD Software Release 7.4.1.
Disable TLS 1.3 on Cisco ASA Software
To disable TLS 1.3 on Cisco ASA Software, set the minimum and maximum TLS version to TLS 1.2 using the ssl server-version and ssl server-max-version commands, as shown in the following example:
ciscoasa# configure terminal
ciscoasa(config)# ssl server-version tlsv1.2 dtlsv1.2
ciscoasa(config)# ssl server-max-version tlsv1.2Disable TLS 1.3 on Cisco FTD Software
To disable TLS 1.3 on Cisco FTD Software, set the minimum and maximum TLS version to TLS 1.2 using Cisco FMC Software and a FlexConfig object. For more information about FlexConfig objects, see the FlexConfig Policies for FTD chapter of the Firepower Management Center Configuration Guide.
To disable TLS 1.3 on Cisco FTD Software, use the following steps:
- Connect to Cisco FMC Software.
- From the menu bar, choose Devices > Platform Settings.
- Add or edit the Platform Settings Policy that is applied to the affected device.
- From the navigation menu on the left, choose SSL.
- From the TLS version drop-down menu, choose TLSv1.2.
- Click Save.
- Choose Objects > Object Management.
- From the navigation menu on the left, choose FlexConfig > FlexConfig Object.
- Click Add FlexConfig Object.
- Enter a name and description (optional) for the object in the appropriate fields.
- From the drop-down menus above the main text box, choose Insert, Deployment: Once, and Type: Append.
- In the main text box, enter ss server-max-version tlsv1.2.
Note: There is no l at the end of the word ss. This is not a typo. If the word ssl is used, Cisco FMC Software will display a validation error when the changes are saved. - Click Save.
- From the menu bar, choose Devices > FlexConfig.
- Edit the existing FlexConfig Policy or add a new one. If a new policy is being added, enter a name and description (optional) for the new policy in the appropriate fields, then click Save.
- From the User Defined drop-down menu on the left, choose the FlexConfig object that was added in step 9.
- Click > to move the object to the Selected Append FlexConfigs pane.
- Click Save.
- From the menu bar, click Deploy to deploy the changes.
- Check the check boxes for devices that are assigned to the policy.
- Check the ignore warnings check box.
Note: When deploying a FlexConfig object, a validation warning will prevent the deployment until the ignore warnings check box is checked. - In the dialog box, click Deploy.
While this workaround has been deployed and was proven successful in a test environment, customers should determine the applicability and effectiveness in their own environment and under their own use conditions. Customers should be aware that any workaround or mitigation that is implemented may negatively impact the functionality or performance of their network based on intrinsic customer deployment scenarios and limitations. Customers should not deploy any workarounds or mitigations before first evaluating the applicability to their own environment and any impact to such environment.
-
Cisco has released free software updates that address the vulnerability described in this advisory. Customers with service contracts that entitle them to regular software updates should obtain security fixes through their usual update channels.
Customers may only install and expect support for software versions and feature sets for which they have purchased a license. By installing, downloading, accessing, or otherwise using such software upgrades, customers agree to follow the terms of the Cisco software license:
https://www.cisco.com/c/en/us/products/end-user-license-agreement.htmlAdditionally, customers may only download software for which they have a valid license, procured from Cisco directly, or through a Cisco authorized reseller or partner. In most cases this will be a maintenance upgrade to software that was previously purchased. Free security software updates do not entitle customers to a new software license, additional software feature sets, or major revision upgrades.
The Cisco Support and Downloads page on Cisco.com provides information about licensing and downloads. This page can also display customer device support coverage for customers who use the My Devices tool.
When considering software upgrades, customers are advised to regularly consult the advisories for Cisco products, which are available from the Cisco Security Advisories page, to determine exposure and a complete upgrade solution.
In all cases, customers should ensure that the devices to be upgraded contain sufficient memory and confirm that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, customers are advised to contact the Cisco Technical Assistance Center (TAC) or their contracted maintenance providers.
Customers Without Service Contracts
Customers who purchase directly from Cisco but do not hold a Cisco service contract and customers who make purchases through third-party vendors but are unsuccessful in obtaining fixed software through their point of sale should obtain upgrades by contacting the Cisco TAC: https://www.cisco.com/c/en/us/support/web/tsd-cisco-worldwide-contacts.html
Customers should have the product serial number available and be prepared to provide the URL of this advisory as evidence of entitlement to a free upgrade.
Cisco ASA, FMC, and FTD Software
To help customers determine their exposure to vulnerabilities in Cisco ASA, FMC, and FTD Software, Cisco provides the Cisco Software Checker. This tool identifies any Cisco security advisories that impact a specific software release and the earliest release that fixes the vulnerabilities that are described in each advisory (“First Fixed”). If applicable, the tool also returns the earliest release that fixes all the vulnerabilities that are described in all the advisories that the Software Checker identifies (“Combined First Fixed”).
To use the tool, go to the Cisco Software Checker page and follow the instructions. Alternatively, use the following form to search for vulnerabilities that affect a specific software release. To use the form, follow these steps:
- Choose which advisories the tool will search—all advisories, only advisories with a Critical or High Security Impact Rating (SIR), or only this advisory.
- Choose the appropriate software.
- Choose the appropriate platform.
- Enter a release number—for example, 9.16.2.11 for Cisco ASA Software or 6.6.7 for Cisco FTD Software.
- Click Check.
Note: For Cisco 3000 Series Industrial Security Appliances (ISAs) that are running Cisco ASA Software, Cisco ASA Software Release 9.16.4.67 has been deferred and replaced by Release 9.16.4.70.
For instructions on upgrading a Cisco FTD device, see the appropriate Cisco FMC upgrade guide.
Additional Resources
For help determining the best Cisco ASA, FMC, or FTD Software release, see the following Recommended Releases documents. If a security advisory recommends a later release, Cisco recommends following the advisory guidance.
Cisco ASA Compatibility
Cisco Secure Firewall ASA Upgrade Guide
Cisco Secure Firewall Threat Defense Compatibility Guide
-
The Cisco Product Security Incident Response Team (PSIRT) is not aware of any public announcements or malicious use of the vulnerability that is described in this advisory.
-
This vulnerability was found by Ilkin Gasimov of Cisco during internal security testing.
-
To learn about Cisco security vulnerability disclosure policies and publications, see the Security Vulnerability Policy. This document also contains instructions for obtaining fixed software and receiving security vulnerability information from Cisco.
-
Version Description Section Status Date 1.0 Initial public release. — Final 2024-OCT-23
-
THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.
A standalone copy or paraphrase of the text of this document that omits the distribution URL is an uncontrolled copy and may lack important information or contain factual errors. The information in this document is intended for end users of Cisco products.