A vulnerability in the processing of SSH connections of Cisco Firepower Management Center (FMC) and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to improper error handling when an SSH session fails to be established. An attacker could exploit this vulnerability by sending a high rate of crafted SSH connections to the instance. A successful exploit could allow the attacker to cause resource exhaustion, resulting in a reboot on the affected device.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Secure_firewall_management_center | Cisco | 6.1.0 (including) | 6.1.0.7 (including) |
| Secure_firewall_management_center | Cisco | 6.2.0 (including) | 6.2.0.6 (including) |
| Secure_firewall_management_center | Cisco | 6.2.2 (including) | 6.2.2.5 (including) |
| Secure_firewall_management_center | Cisco | 6.2.3 (including) | 6.2.3.18 (including) |
| Secure_firewall_management_center | Cisco | 6.3.0 (including) | 6.3.0.5 (including) |
| Secure_firewall_management_center | Cisco | 6.4.0 (including) | 6.4.0.15 (including) |
| Secure_firewall_management_center | Cisco | 6.5.0 (including) | 6.5.0.5 (including) |
| Secure_firewall_management_center | Cisco | 6.7.0 (including) | 6.7.0.3 (including) |
| Secure_firewall_management_center | Cisco | 6.2.1 (including) | 6.2.1 (including) |
| Secure_firewall_management_center | Cisco | 6.6.0 (including) | 6.6.0 (including) |
| Secure_firewall_management_center | Cisco | 6.6.0.1 (including) | 6.6.0.1 (including) |
| Secure_firewall_management_center | Cisco | 6.6.1 (including) | 6.6.1 (including) |
| Secure_firewall_management_center | Cisco | 6.6.3 (including) | 6.6.3 (including) |
| Secure_firewall_management_center | Cisco | 6.6.4 (including) | 6.6.4 (including) |
| Secure_firewall_management_center | Cisco | 6.6.5 (including) | 6.6.5 (including) |
| Secure_firewall_management_center | Cisco | 6.6.5.1 (including) | 6.6.5.1 (including) |
| Secure_firewall_management_center | Cisco | 6.6.5.2 (including) | 6.6.5.2 (including) |
| Secure_firewall_management_center | Cisco | 7.0.0 (including) | 7.0.0 (including) |
| Secure_firewall_management_center | Cisco | 7.0.0.1 (including) | 7.0.0.1 (including) |
| Secure_firewall_management_center | Cisco | 7.0.1 (including) | 7.0.1 (including) |
| Secure_firewall_management_center | Cisco | 7.0.1.1 (including) | 7.0.1.1 (including) |
| Secure_firewall_management_center | Cisco | 7.0.2 (including) | 7.0.2 (including) |
| Secure_firewall_management_center | Cisco | 7.0.2.1 (including) | 7.0.2.1 (including) |
| Secure_firewall_management_center | Cisco | 7.0.3 (including) | 7.0.3 (including) |
| Secure_firewall_management_center | Cisco | 7.0.4 (including) | 7.0.4 (including) |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.