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-26671 TAIWAN SECOM CO., LTD., a xDoor Access Control and Personnel Attendance Management system - Hard-coded Credentials — Personnel Attendance Management system 7.3 High2022-04-07
CVE-2021-27430 GE UR family hardcoded credentials — UR bootloader binary 8.4 High2022-03-23
CVE-2022-25246 PTC Axeda agent and Axeda Desktop Server Use of Hard-Coded Credentials — Axeda agent 9.8 Critical2022-03-16
CVE-2022-23402 Yokogawa Electric 信任管理问题漏洞 — CENTUM VP 8.8 -2022-03-11
CVE-2022-21194 Yokogawa Electric 信任管理问题漏洞 — CENTUM VP 8.8 -2022-03-11
CVE-2022-22765 BD Viper LT System - Hardcoded Credentials — BD Viper LT System 8.0 High2022-02-12
CVE-2022-22766 BD Pyxis Products - Hardcoded Credentials — BD Pyxis Anesthesia Station ES 7.0 High2022-02-11
CVE-2022-22813 Schneider Electric Easergy P40 信任管理问题漏洞 — Easergy P40 Series model numbers with Ethernet option bit as Q, R, S (All PX4X firmware Versions) 8.1 -2022-02-09
CVE-2021-45106 Siemens Sicam Toolbox II 信任管理问题漏洞 — SICAM TOOLBOX II 6.5 -2022-02-09
CVE-2022-22722 Schneider Electric Easergy P5 信任管理问题漏洞 — Easergy P5 7.4 -2022-02-04
CVE-2021-44464 Fresenius Kabi Agilia Connect Infusion System hard coded credentials — Vigilant Software Suite (Mastermed Dashboard) 6.3 Medium2022-01-21
CVE-2022-22056 Le-yan Co., Ltd. dental management system - Hard-coded Credentials — Dental Management System 9.8 Critical2022-01-14
CVE-2021-45033 Siemens SICAM A8000 CP-8000 信任管理问题漏洞 — CP-8000 MASTER MODULE WITH I/O -25/+70°C 8.8 -2022-01-11
CVE-2022-21669 Bot token exposed in main.py — pudding-bot 9.1 Critical2022-01-11
CVE-2021-45458 Hardcoded credentials — Apache Kylin 7.5 -2022-01-06
CVE-2021-32993 Philips IntelliBridge EC 40 and EC 80 Hub Use of Hard-coded Credentials — IntelliBridge EC 40 Hub 8.1 High2021-12-27
CVE-2021-35232 Hard credentials discovered in SolarWinds Web Help Desk which allows to execute Arbitrary Hibernate Queries — Web Help Desk 6.8 Medium2021-12-27
CVE-2021-26611 HejHome IP Camera use of hard-coded credentials vulnerability — GKW-IC052 8.1 High2021-11-26
CVE-2021-41299 ECOA BAS controller - Use of Hard-coded Credentials — ECS Router Controller ECS (FLASH) 9.8 Critical2021-09-30
CVE-2021-21913 D-LINK DIR-3040 信任管理问题漏洞 — D-Link 9.8 -2021-09-23
CVE-2021-34571 Hard-coded Credentials in Enbra Wireless M-Bus devices — AT-WMBUS-16-2 6.5 Medium2021-09-16
CVE-2021-34565 In WirelessHART-Gateway versions 3.0.7 to 3.0.9 hard-coded credentials have been found — WHA-GW-F2D2-0-AS- Z2-ETH 9.8 Critical2021-08-31
CVE-2021-27503 Ypsomed mylife App 信任管理问题漏洞 — Ypsomed mylife Cloud, mylife Mobile Application 6.5 -2021-08-02
CVE-2021-31579 Akkadian Provisioning Manager Engine (PME) Hard-Coded Credentials — Provisioning Manager Engine (PME) 8.2 High2021-07-22
CVE-2021-22730 EVlink City、EVlink Parking、EVlink Smart Wallbox 信任管理问题漏洞 — EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink Parking (EVW2 / EVF2 / EV.2 all versions prior to R8 V3.4.0.1), and EVlink Smart Wallbox (EVB1A all versions prior to R8 V3.4.0.1 ) 9.8 -2021-07-21
CVE-2021-22707 Multiple Schneider Electric EVlink Charging Stations 信任管理问题漏洞 — EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink Parking (EVW2 / EVF2 / EV.2 all versions prior to R8 V3.4.0.1), and EVlink Smart Wallbox (EVB1A all versions prior to R8 V3.4.0.1 ) 9.8 -2021-07-21
CVE-2020-5349 Dell EMC Networking S4100 和 S5200 信任管理问题漏洞 — Networking 9.8 Critical2021-07-19
CVE-2021-35961 TAIWAN SECOM CO., LTD., Door Access Control and Personnel Attendance Management system - Use of Hard-coded Credentials — Door Access Control and Personnel Attendance Management system 9.8 Critical2021-07-16
CVE-2021-21820 D-LINK DIR-3040 信任管理问题漏洞 — D-Link 9.8 -2021-07-16
CVE-2021-0279 Contrail Cloud: Hardcoded credentials for RabbitMQ service — Contrail Cloud 8.6 High2021-07-15

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