CWE-798 Use of Hard-coded Credentials

The product contains hard-coded credentials, such as a password or cryptographic key.

• Access Control: Bypass Protection Mechanism — If hard-coded passwords are used, it is almost certain that malicious users will gain access to the account in question. Any user of the product that hard-codes passwords may be able to extract the password. Client-side systems with hard-coded passwords pose even more of a threat, since the extraction of a password from a binary is usually very simple. • Integrity, Confidentiality, Availability, Access Control, Other: Read Application Data, Gain Privileges or Assume Identity, Execute Unauthorized Code or Commands, Other — This weakness can lead to the exposure of resources or functionality to unintended actors, possibly providing attackers with sensitive information or even execute arbitrary code. If the password is ever discovered or published (a common occurrence on the Internet), then anybody with knowledge of this password can access the product. Finally, since all installations of the product will have the same password, even across different organizations, this enables massive attacks such as worms to take place.

• [Architecture and Design] For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible [REF-7]. In Windows environments, the Encrypted File System (EFS) may provide some protection. • [Architecture and Design] For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key. • [Architecture and Design] If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection. • [Architecture and Design] For inbound authentication using passwords: apply strong one-way hashes to 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 handling an incoming password during authentication, take the hash of the password and compare it to the saved hash. Use randomly assigned salts for each separate hash that is generated. 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. • [Architecture and Design] For front-end to back-end connections: Three solutions are possible, although none are complete. • The first suggestion involves the use of generated passwords or keys that are changed automatically and must be entered at given time intervals by a system administrator. These passwords will be held in memory and only be valid for the time intervals. • Next, the passwords or keys should be limited at the back end to only performing actions valid for the front end, as opposed to having full access. • Finally, the messages sent should be tagged and checksummed with time sensitive values so as to prevent replay-style attacks.

• Black Box: Credential storage in configuration files is findable using black box methods, but the use of hard-coded credentials for an incoming authentication routine typically involves an account that is not visible outside of the code. • Automated Static Analysis: Automated white box techniques have been published for detecting hard-coded credentials for incoming authentication, but there is some expert disagreement regarding their effectiveness and applicability to a broad range of methods. • Manual Static Analysis: This weakness may be detectable using manual code analysis. Unless authentication is decentralized and applied throughout the product, there can be sufficient time for the analyst to find incoming authentication routines and examine the program logic looking for usage of hard-coded credentials. Configuration files could also be analyzed. • Manual Dynamic Analysis: For hard-coded credentials in incoming authentication: use monitoring tools that examine the product's process as it interacts with the operating system and the network. This technique is useful in cases when source code is unavailable, if the product was not developed by you, or if you want to verify that the build phase did not introduce any new weaknesses. Examples include debuggers that directly attach to the running process; system-call tracing utilities such as truss (Solaris) and strace (Linux); system activity monitors such as FileMon, RegMon, Process Monitor, and other Sysinternals utilities (Windows); and sniffers and protocol analyzers that monitor network traffic. Attach the monitor to the process and perform a login. Using call trees or similar artifacts from the output, examine the associated behaviors and see if any of them appear to be comparing the input to a fixed string or value. • Automated Static Analysis - Binary or Bytecode: According to SOAR [REF-1479], the following detection techniques may be useful: Cost effective for partial coverage: • Bytecode Weakness Analysis - including disassembler + source code weakness analysis • Binary Weakness Analysis - including disassembler + source code weakness analysis • Manual Static Analysis - Binary or Bytecode: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Binary / Bytecode disassembler - then use manual analysis for vulnerabilities & anomalies • Dynamic Analysis with Manual Results Interpretation: According to SOAR [REF-1479], the following detection techniques may be useful: Cost effective for partial coverage: • Network Sniffer • Forced Path Execution • Manual Static Analysis - Source Code: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Focused Manual Spotcheck - Focused manual analysis of source • Manual Source Code Review (not inspections) • Automated Static Analysis - Source Code: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Source code Weakness Analyzer • Context-configured Source Code Weakness Analyzer • Automated Static Analysis: According to SOAR [REF-1479], the following detection techniques may be useful: Cost effective for partial coverage: • Configuration Checker • Architecture or Design Review: According to SOAR [REF-1479], the following detection techniques may be useful: Highly cost effective: • Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.) • Formal Methods / Correct-By-Construction

• CVE-2022-40263: Software for biological cell analysis has hard-coded credentials, leading to leak of Protected Health Information (PHI) • CVE-2022-29953: Condition Monitor firmware has a maintenance interface with hard-coded credentials • CVE-2022-29960: Engineering Workstation uses hard-coded cryptographic keys that could allow for unauthorized filesystem access and privilege escalation • CVE-2022-29964: Distributed Control System (DCS) has hard-coded passwords for local shell access • CVE-2022-30997: Programmable Logic Controller (PLC) has a maintenance service that uses undocumented, hard-coded credentials • CVE-2022-30314: Firmware for a Safety Instrumented System (SIS) has hard-coded credentials for access to boot configuration • CVE-2022-30271: Remote Terminal Unit (RTU) uses a hard-coded SSH private key that is likely to be used in typical deployments • CVE-2021-37555: Telnet service for IoT feeder for dogs and cats has hard-coded password [REF-1288] • CVE-2021-35033: Firmware for a WiFi router uses a hard-coded password for a BusyBox shell, allowing bypass of authentication through the UART port • CVE-2012-3503: Installation script has a hard-coded secret token value, allowing attackers to bypass authentication • CVE-2010-2772: SCADA system uses a hard-coded password to protect back-end database containing authorization information, exploited by Stuxnet worm • CVE-2010-2073: FTP server library uses hard-coded usernames and passwords for three default accounts • CVE-2010-1573: Chain: Router firmware uses hard-coded username and password for access to debug functionality, which can be used to execute arbitrary code • CVE-2008-2369: Server uses hard-coded authentication key • CVE-2008-0961: Backup product uses hard-coded username and password, allowing attackers to bypass authentication via the RPC interface • CVE-2008-1160: Security appliance uses hard-coded password allowing attackers to gain root access • CVE-2006-7142: Drive encryption product stores hard-coded cryptographic keys for encrypted configuration files in executable programs • CVE-2005-3716: VoIP product uses hard-coded public credentials that cannot be changed, which allows attackers to obtain sensitive information • CVE-2005-3803: VoIP product uses hard coded public and private SNMP community strings that cannot be changed, which allows remote attackers to obtain sensitive information • CVE-2005-0496: Backup product contains hard-coded credentials that effectively serve as a back door, which allows remote attackers to access the file system