CVE Vulnerabilities

CVE-2024-20412

Use of Hard-coded Password

Published: Oct 23, 2024 | Modified: Nov 05, 2024
CVSS 3.x
8.4
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

A vulnerability in Cisco Firepower Threat Defense (FTD) Software for Cisco Firepower 1000, 2100, 3100, and 4200 Series could allow an unauthenticated, local attacker to access an affected system using static credentials. This vulnerability is due to the presence of static accounts with hard-coded passwords on an affected system. An attacker could exploit this vulnerability by logging in to the CLI of an affected device with these credentials. A successful exploit could allow the attacker to access the affected system and retrieve sensitive information, perform limited troubleshooting actions, modify some configuration options, or render the device unable to boot to the operating system, requiring a reimage of the device.

Weakness

The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.

Affected Software

Name Vendor Start Version End Version
Firepower_threat_defense Cisco 7.1.0 (including) 7.1.0 (including)
Firepower_threat_defense Cisco 7.1.0.1 (including) 7.1.0.1 (including)
Firepower_threat_defense Cisco 7.1.0.2 (including) 7.1.0.2 (including)
Firepower_threat_defense Cisco 7.1.0.3 (including) 7.1.0.3 (including)
Firepower_threat_defense Cisco 7.2.0 (including) 7.2.0 (including)
Firepower_threat_defense Cisco 7.2.0.1 (including) 7.2.0.1 (including)
Firepower_threat_defense Cisco 7.2.1 (including) 7.2.1 (including)
Firepower_threat_defense Cisco 7.2.2 (including) 7.2.2 (including)
Firepower_threat_defense Cisco 7.2.3 (including) 7.2.3 (including)
Firepower_threat_defense Cisco 7.2.4 (including) 7.2.4 (including)
Firepower_threat_defense Cisco 7.2.4.1 (including) 7.2.4.1 (including)
Firepower_threat_defense Cisco 7.2.5 (including) 7.2.5 (including)
Firepower_threat_defense Cisco 7.2.5.1 (including) 7.2.5.1 (including)
Firepower_threat_defense Cisco 7.2.5.2 (including) 7.2.5.2 (including)
Firepower_threat_defense Cisco 7.2.6 (including) 7.2.6 (including)
Firepower_threat_defense Cisco 7.2.7 (including) 7.2.7 (including)
Firepower_threat_defense Cisco 7.3.0 (including) 7.3.0 (including)
Firepower_threat_defense Cisco 7.3.1 (including) 7.3.1 (including)
Firepower_threat_defense Cisco 7.3.1.1 (including) 7.3.1.1 (including)
Firepower_threat_defense Cisco 7.3.1.2 (including) 7.3.1.2 (including)
Firepower_threat_defense Cisco 7.4.0 (including) 7.4.0 (including)
Firepower_threat_defense Cisco 7.4.1 (including) 7.4.1 (including)
Firepower_threat_defense Cisco 7.4.1.1 (including) 7.4.1.1 (including)

Extended Description

There are two main variations of a hard-coded password:

Potential Mitigations

  • For inbound authentication: apply strong one-way hashes to your passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When receiving an incoming password during authentication, take the hash of the password and compare it to the hash that you have saved.
  • Use randomly assigned salts for each separate hash that you generate. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.
  • For front-end to back-end connections: Three solutions are possible, although none are complete.

References