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-2022-29477 Abode Iota 信任管理问题漏洞 — iota All-In-One Security Kit 9.8 -2022-10-25
CVE-2022-38117 Juiker app - Hard-coded Credentials — Juiker app 5.5 Medium2022-10-24
CVE-2022-38420 Adobe ColdFusion Use of Hard-coded Credentials Application denial-of-service — ColdFusion 7.5 High2022-10-14
CVE-2022-39273 Default OAuth Authorization Server secret in FlyteAdmin — flyteadmin 4.8 Medium2022-10-06
CVE-2022-20844 Cisco Software-Defined Application Visibility and Control on Cisco vManage Static Username and Password Vulnerability — Cisco SD-WAN vManage 5.3 Medium2022-09-30
CVE-2022-28812 Use of Hard-coded Credentials in UWP3.0 allows SuperUser authentication bypass in Car Park Server. — UWP 3.0 Monitoring Gateway and Controller 9.8 Critical2022-09-28
CVE-2022-22522 Hard-coded credentials in Carlo Gavazzi UWP3.0 allows for authentication bypass and full control of the device — UWP 3.0 Monitoring Gateway and Controller 9.8 Critical2022-09-28
CVE-2022-3214 Delta Electronics DIAEnergy Use of Hard-coded Credentials — DIAEnergy 9.8 Critical2022-09-16
CVE-2022-38069 Contec Health CMS8000 — CMS8000 CONTEC ICU CCU Vital Signs Patient Monitor 4.3 Medium2022-09-13
CVE-2022-38116 Le-yan Co., Ltd. Personnel and Salary Management System - Hard-coded password — Personnel and Salary Management System 9.8 Critical2022-08-30
CVE-2022-32965 ITPison OMICARD EDM - Use of Hard-coded Credentials — OMICARD EDM 9.8 Critical2022-08-04
CVE-2022-35866 Vinchin Backup and Recovery 信任管理问题漏洞 — Backup and Recovery 9.8 -2022-08-03
CVE-2022-26138 Atlassian Confluence Server 信任管理问题漏洞 — Questions For Confluence 9.8 -2022-07-20
CVE-2022-2107 ICSA-22-200-01 MiCODUS MV720 GPS tracker Use of Hard-coded Credentials — MV720 9.8 Critical2022-07-20
CVE-2020-36547 GE Voluson S8 Service Browser hard-coded credentials — Voluson S8 5.9 Medium2022-06-17
CVE-2022-31619 Siemens Teamcenter 信任管理问题漏洞 — Teamcenter V12.4 9.1 -2022-06-14
CVE-2022-26476 Siemens Spectrum Power 信任管理问题漏洞 — Spectrum Power 4 8.8 -2022-06-14
CVE-2022-30234 Schneider Electric PowerLogic ION Setup 信任管理问题漏洞 — Wiser Smart 9.4 Critical2022-06-02
CVE-2021-33014 KUKA KR C4 - Use of Hard-Coded Credentials — KR C4 8.8 High2022-05-26
CVE-2021-33016 KUKA KR C4 - Use of Hard-Coded Credentials — KR C4 9.8 Critical2022-05-26
CVE-2013-10002 Telecommunication Software SAMwin Contact Center Suite Credential SAMwinLIBVB.dll getCurrentDBVersion hard-coded credentials — SAMwin Contact Center Suite 6.5 Medium2022-05-24
CVE-2021-42850 Lenovo Personal Cloud Storage 信任管理问题漏洞 — Personal Cloud Storage A1 8.8 High2022-05-18
CVE-2021-42849 Lenovo Personal Cloud Storage 授权问题漏洞 — Personal Cloud Storage A1 6.8 Medium2022-05-18
CVE-2022-23942 Apache Doris hardcoded cryptography initialization — Apache Doris(Incubating) 7.5 -2022-04-26
CVE-2022-26672 ASUS WebStorage - Use of Hard-coded Credentials — WebStorage 7.3 High2022-04-22
CVE-2020-25168 B. Braun SpaceCom, Battery Pack SP with Wi-Fi, and Data module compactplus — SpaceCom 3.3 Low2022-04-14
CVE-2021-40422 Swift Sensors Gateway SG3-1010 信任管理问题漏洞 — Swift Sensors Gateway 10.0 Critical2022-04-14
CVE-2021-40390 MOXA Moxa MXView 信任管理问题漏洞 — MXView Series 9.8 -2022-04-14
CVE-2022-27506 Citrix SD-WAN 信任管理问题漏洞 — Citrix SD-WAN 6.7 -2022-04-13
CVE-2022-22560 Dell Technologies Dell PowerScale OneFS 信任管理问题漏洞 — PowerScale OneFS 7.1 High2022-04-12

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