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-2023-45226 BIG-IP Next SPK SSH vulnerability — BIG-IP Next SPK 7.4 High2023-10-10
CVE-2023-36380 Siemens CP-8031 信任管理问题漏洞 — CP-8031 MASTER MODULE 9.8 Critical2023-10-10
CVE-2023-2306 Qognify NiceVision Use of Hard-coded Credentials — NiceVision 10.0 Critical2023-10-05
CVE-2023-20101 Cisco Emergency Responder 信任管理问题漏洞 — Cisco Emergency Responder 9.8 Critical2023-10-04
CVE-2022-47891 Admin password reset in NetMan 204 — Netman-204 8.1 High2023-10-03
CVE-2023-5318 Use of Hard-coded Credentials in microweber/microweber — microweber/microweber 9.4 -2023-09-30
CVE-2023-20034 Cisco SD-WAN vManage 安全漏洞 — Cisco SD-WAN vManage 7.5 High2023-09-27
CVE-2023-41878 Weak password of selenium VNC in MeterSphere — metersphere 4.6 Medium2023-09-26
CVE-2023-5074 Authentication Bypass in D-Link D-View 8 — D-View 8 9.8 Critical2023-09-20
CVE-2023-40717 FortiTester 信任管理问题漏洞 — FortiTester 5.0 Medium2023-09-13
CVE-2023-39422 Use of Hard-coded Credentials in multiple /irmdata/api/ endpoints — IRM Next Generation 6.5 Medium2023-09-07
CVE-2023-39421 Use of Hard-coded Credentials in RDPWin.dll — IRM Next Generation 7.7 High2023-09-07
CVE-2023-39420 Use of Hard-coded Credentials in RDPCore.dll — IRM Next Generation 9.9 Critical2023-09-07
CVE-2023-31173 Use of Hard-coded Credentials — SEL-5037 SEL Grid Configurator 7.7 High2023-08-31
CVE-2023-38026 SpotCam Co., Ltd. SpotCamFHD - Use of Hard-coded Cryptographic Key -2 — SpotCam FHD 2 9.8 Critical2023-08-28
CVE-2023-38024 SpotCam Co., Ltd. SpotCamFHD - Use of Hard-coded Cryptographic Key -1 — SpotCam FHD 2 9.8 Critical2023-08-28
CVE-2022-3744 Lenovo Notebook 信任管理问题漏洞 — Notebook 6.7 Medium2023-08-23
CVE-2023-4204 NPort IAW5000A-I/O Series Hardcoded Credential Vulnerability — NPort IAW5000A-I/O Series 5.4 Medium2023-08-16
CVE-2023-3264 Dataprobe 信任管理问题漏洞 — iBoot PDU 6.7 Medium2023-08-14
CVE-2023-3262 Dataprobe 信任管理问题漏洞 — iBoot PDU 6.7 Medium2023-08-14
CVE-2023-37857 PHOENIX CONTACT: Use of Hard-coded Credentials in WP 6xxx Web panels — WP 6070-WVPS 3.8 Low2023-08-09
CVE-2023-37215 JBL soundbar multibeam 5.1 - CWE-798: Use of Hard-coded Credentials — soundbar multibeam 6.2 Medium2023-07-30
CVE-2023-32227 Synel SYnergy Fingerprint Terminals - CWE-798: Use of Hard-coded Credentials — SYnergy Fingerprint Terminals 9.8 Critical2023-07-30
CVE-2023-37287 SmartBPM.NET - Use of Hard-Coded Credentials - 2 — SmartBPM.NET 9.1 Critical2023-07-10
CVE-2023-37286 SmartBPM.NET - Use of Hard-Coded Credentials - 1 — SmartBPM.NET 9.8 Critical2023-07-10
CVE-2023-35987 PiiGAB M-Bus Use of Hard-coded Credentials — M-Bus SoftwarePack 9.8 Critical2023-07-06
CVE-2023-34473 Usage of Hard-coded Credentials — MegaRAC_SPx 6.6 Medium2023-07-05
CVE-2023-2611 Advantech R-SeeNet Use of Hard-coded Credentials — R-SeeNet 9.8 Critical2023-06-22
CVE-2023-32274 Enphase Installer Toolkit Android App Use of Hard-coded Credentials — Enphase Installer Toolkit 8.6 High2023-06-20
CVE-2023-33920 Siemens CP-8031 信任管理问题漏洞 — CP-8031 MASTER MODULE 6.8 Medium2023-06-13

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