Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CWE-798 (使用硬编码的凭证) — Vulnerability Class 559

559 vulnerabilities classified as CWE-798 (使用硬编码的凭证). AI Chinese analysis included.

CWE-798 represents a critical security weakness where authentication mechanisms rely on static, embedded credentials rather than dynamic verification. This flaw typically manifests as default administrative accounts with simple, hard-coded passwords or cryptographic keys stored directly within the source code or configuration files. Attackers exploit this vulnerability by scanning for these predictable credentials, gaining immediate, unauthorized access to sensitive systems without needing to bypass complex security controls. To mitigate this risk, developers must eliminate static secrets entirely, implementing robust credential management solutions such as secure vaults, environment variables, or hardware security modules. Additionally, enforcing strong password policies, regular key rotation, and multi-factor authentication ensures that access rights are dynamic and secure, significantly reducing the attack surface against unauthorized entry.

MITRE CWE Description
The product contains hard-coded credentials, such as a password or cryptographic key. There are two main variations: Inbound: the product contains an authentication mechanism that checks the input credentials against a hard-coded set of credentials. In this variant, a default administration account is created, and a simple password is hard-coded into the product and associated with that account. This hard-coded password is the same for each installation of the product, and it usually cannot be changed or disabled by system administrators without manually modifying the program, or otherwise patching the product. It can also be difficult for the administrator to detect. Outbound: the product connects to another system or component, and it contains hard-coded credentials for connecting to that component. This variant applies to front-end systems that authenticate with a back-end service. The back-end service may require a fixed password that can be easily discovered. The programmer may simply hard-code those back-end credentials into the front-end product.
Common Consequences (2)
Access ControlBypass 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 extracti…
Integrity, Confidentiality, Availability, Access Control, OtherRead 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 thi…
Mitigations (5)
Architecture and DesignFor 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 …
Architecture and DesignFor 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 DesignIf 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 DesignFor 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 ra…
Architecture and DesignFor 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 th…
Examples (2)
The following code uses a hard-coded password to connect to a database:
... DriverManager.getConnection(url, "scott", "tiger"); ...
Bad · Java
javap -c ConnMngr.class 22: ldc #36; //String jdbc:mysql://ixne.com/rxsql 24: ldc #38; //String scott 26: ldc #17; //String tiger
Attack
The following code is an example of an internal hard-coded password in the back-end:
int VerifyAdmin(char *password) { if (strcmp(password, "Mew!")) { printf("Incorrect Password!\n"); return(0) } printf("Entering Diagnostic Mode...\n"); return(1); }
Bad · C
int VerifyAdmin(String password) { if (!password.equals("Mew!")) { return(0) } //Diagnostic Mode return(1); }
Bad · Java
CVE IDTitleCVSSSeverityPublished
CVE-2024-0390 Hard-coded credentials in iZZi connect application — iZZi connect 4.6 -2024-02-15
CVE-2023-4539 Hardcoded password in Comarch ERP XL — ERP XL 7.5 High2024-02-15
CVE-2023-6409 Schneider Electric Modicon M340 信任管理问题漏洞 — EcoStruxure Control Expert 7.7 High2024-02-14
CVE-2024-23816 Siemens Location Intelligence Perpetual 信任管理问题漏洞 — Location Intelligence Perpetual Large 9.8 Critical2024-02-13
CVE-2024-22313 IBM Storage Defender - Resiliency Service information disclosure — Storage Defender - Resiliency Service 6.2 Medium2024-02-10
CVE-2024-21764 Use of Hard-Coded Credentials in Rapid SCADA — Rapid SCADA 9.8 Critical2024-02-01
CVE-2023-46706 MachineSense FeverWarn Use of Hard-coded Credentials — FeverWarn 9.1 Critical2024-02-01
CVE-2024-1039 Use of Hard-coded Credentials in Gessler GmbH WEB-MASTER — WEB-MASTER 9.8 Critical2024-02-01
CVE-2024-23619 IBM Merge Healthcare eFilm Workstation Hardcoded Credentials — eFilm Workstation 9.8 Critical2024-01-25
CVE-2023-28897 Hard-coded password for UDS services — MIB3 Infotainment Unit 4.0 Medium2024-01-12
CVE-2023-49253 Predefined root password — H8951-4G-ESP 9.8 -2024-01-12
CVE-2023-48251 Bosch Nexo cordless nutrunner 安全漏洞 — Nexo cordless nutrunner NXA015S-36V (0608842001) 8.1 High2024-01-10
CVE-2023-48250 Bosch Nexo cordless nutrunner 安全漏洞 — Nexo cordless nutrunner NXA015S-36V (0608842001) 8.1 High2024-01-10
CVE-2023-47704 IBM Security Guardium Key Lifecycle Manager information disclosure — Security Guardium Key Lifecycle Manager 4.0 Medium2023-12-20
CVE-2023-43870 Paxton Access Net2 信任管理问题漏洞 — Net2 8.1 High2023-12-19
CVE-2023-48388 Multisuns EasyLog web+ - Use of Hard-coded Password — EasyLog web+ 9.8 Critical2023-12-15
CVE-2023-48374 SmartStar Software CWS Web-Base - Use of Hard-coded Credentials — CWS Web-Base 6.5 Medium2023-12-15
CVE-2023-43583 Zoom 安全漏洞 — Zoom Mobile App for Android, Zoom Mobile App for iOS and Zoom SDK 4.9 Medium2023-12-13
CVE-2023-39169 SENEC: Storage Box V1,V2 and V3 using default credentials — Storage Box V1 9.8 Critical2023-12-07
CVE-2023-40463 Use of Hard-Coded Credentials — ALEOS 8.1 High2023-12-04
CVE-2023-29064 Hardcoded Secrets — FACSChorus 4.1 Medium2023-11-28
CVE-2023-36013 PowerShell Information Disclosure Vulnerability — PowerShell 7.2 6.5 Medium2023-11-20
CVE-2023-44296 Dell ELab 信任管理问题漏洞 — Mobility - E-Lab Navigator 8.4 High2023-11-16
CVE-2023-40719 Fortinet FortiAnalyzer 安全漏洞 — FortiAnalyzer 4.1 Medium2023-11-14
CVE-2023-33304 Fortinet FortiClient 安全漏洞 — FortiClientWindows 4.4 Medium2023-11-14
CVE-2023-5777 Weintek EasyBuilder Pro Use of Hard-coded Credentials — EasyBuilder Pro 9.8 Critical2023-11-06
CVE-2023-46102 Bosch ctrlX HMI Web Panel 信任管理问题漏洞 — ctrlX HMI Web Panel - WR21 (WR2107) 8.8 High2023-10-25
CVE-2023-41372 Bosch ctrlX HMI Web Panel WR21 信任管理问题漏洞 — ctrlX HMI Web Panel - WR21 (WR2107) 7.8 High2023-10-25
CVE-2022-22466 IBM Security Verify Governance information disclosure — Security Verify Governance 6.8 Medium2023-10-23
CVE-2023-33836 IBM Security Verify Governance information disclosure — Security Verify Governance 5.3 Medium2023-10-16

Vulnerabilities classified as CWE-798 (使用硬编码的凭证) represent 559 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.