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-2026-4475 Yi Technology YI Home Camera ipc hard-coded credentials — YI Home Camera 8.8 High2026-03-20
CVE-2026-4219 INDEX Conferences & Exhibitions Organization YWF BPOF APGCS App ae.index.apgcs BuildConfig.java hard-coded credentials — YWF BPOF APGCS App 3.3 Low2026-03-16
CVE-2026-4216 i-SENS SmartLog App air.SmartLog.android hard-coded credentials — SmartLog App 5.3 Medium2026-03-16
CVE-2016-20031 ZKTeco ZKBioSecurity 3.0 Local Authorization Bypass via visLogin.jsp — ZKTeco ZKBioSecurity 5.5 Medium2026-03-15
CVE-2016-20026 ZKTeco ZKBioSecurity 3.0 Hardcoded Credentials Remote Code Execution — ZKTeco ZKBioSecurity 9.8 Critical2026-03-15
CVE-2026-3873 Legacy built-in user account — Avantra 7.2 High2026-03-13
CVE-2026-28255 Use of Hard-coded Credentials vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge — Tracer SC 9.8AICriticalAI2026-03-12
CVE-2019-25470 eWON Firmware 12.2-13.0 Authentication Bypass via wsdReadForm — eWON 7.5 High2026-03-11
CVE-2026-24448 Micro Research MR-GM5L-S1和Micro Research MR-GM5A-L1 信任管理问题漏洞 — MR-GM5L-S1 9.8AICriticalAI2026-03-11
CVE-2025-13957 Schneider Electric EcoStruxure IT Data Center Expert 信任管理问题漏洞 — EcoStruxure™ IT Data Center Expert (Formerly known as StruxureWare Data Center Expert) 9.8AICriticalAI2026-03-10
CVE-2025-41710 Use of Hard-coded Credentials in power analyzer — UMG 96RM-E 24V(5222063) 6.5 Medium2026-03-10
CVE-2026-29023 Keygraph Shannon Hard-coded Router API Key — Shannon 7.3 High2026-03-09
CVE-2026-29120 Insecure, Hardcoded Root Password Stored in Anaconda Configuration File On IDC SFX2100 Satellite Receiver — IDC SFX2100 SuperFlex Satellite Receiver 7.8AIHighAI2026-03-04
CVE-2026-29119 Hardcoded and Insecure Credentials for "Admin" Account providing Telnet Access on IDC SFX2100 Satellite Receiver — SFX2100 Series SuperFlex SatelliteReceiver 9.8AICriticalAI2026-03-04
CVE-2026-28778 Hardcoded FTP Credentials and LPE(via Insecure Permissions) for `xd` Local Account on IDC SFX2100 — IDC SFX2100 SuperFlex Satellite Receiver 9.8AICriticalAI2026-03-04
CVE-2026-28777 Hardcoded and Insecure Credentials for "User" Local Account with SSH Access On IDC SFX2100 Satellite Receiver — SFX2100 Satellite Receiver 9.8AICriticalAI2026-03-04
CVE-2026-28776 Hardcoded and Insecure Credentials for "monitor" account with SSH Access On IDC SFX2100 Satellite Receiver — IDC SFX2100 SuperFlex Satellite Receiver 9.8AICriticalAI2026-03-04
CVE-2026-27167 Gradio: Mocked OAuth Login Exposes Server Credentials and Uses Hardcoded Session Secret — gradio--2026-02-27
CVE-2025-1242 Administrative Credentials Can Be Extracted Through Gardyn API Responses — Home Kit 9.1 Critical2026-02-25
CVE-2025-13776 Hard-coded database credentials in Finka software — Finka-FK 7.8 -2026-02-24
CVE-2026-27507 Binardat 10G08-0800GSM Network Switch Hard-coded Credentials — 10G08-0800GSM Network Switch 9.8 Critical2026-02-24
CVE-2026-2702 Beetel 777VR1 WPA2 PSK hard-coded credentials — 777VR1 3.1 Low2026-02-19
CVE-2026-22769 Dell RecoverPoint for Virtual Machines 信任管理问题漏洞 — RecoverPoint for Virtual Machines 10.0 Critical2026-02-17
CVE-2025-33089 Multiple Vulnerabilities in IBM Concert Software. — Concert 6.5 Medium2026-02-17
CVE-2026-23647 Glory RBG-100 Recycler System Hard-coded OS Credentials — RBG-100 9.8 Critical2026-02-17
CVE-2026-2616 Beetel 777VR1 Web Management hard-coded credentials — 777VR1 8.8 High2026-02-17
CVE-2026-26334 Calero VeraSMART < 2026 R1 Hardcoded Static AES Keys Allow Decryption of Service Credentials — VeraSMART 7.8AIHighAI2026-02-13
CVE-2019-25322 Heatmiser Netmonitor 3.03 - Hardcoded Credentials — Heatmiser Netmonitor 7.5 High2026-02-12
CVE-2026-26218 newbee-mall Default Seeded Administrator Credentials Allow Account Takeover — newbee-mall 9.8 Critical2026-02-12
CVE-2020-37135 AMSS++ 4.7 - Backdoor Admin Account — AMSS++ 7.5 High2026-02-06

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