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

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

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

684 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 Control Bypass 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, Other Read 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 Design For 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 Design For 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 Design If 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 Design For 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 Design For 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 ID Title CVSS Severity Published
CVE-2022-50696 SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x Hardcoded Credentials Authentication Bypass — Impact/Pulse/First 9.8 Critical 2025-12-30
CVE-2025-68926 RustFS has a gRPC Hardcoded Token Authentication Bypass — rustfs 9.8 Critical 2025-12-30
CVE-2019-25241 FaceSentry Access Control System 6.4.8 Remote SSH Root Access — FaceSentry Access Control System 7.5 High 2025-12-24
CVE-2018-25138 FLIR AX8 Thermal Camera 1.32.16 Hard-Coded Credentials Authentication Bypass — FLIR AX8 Thermal Camera 9.8 Critical 2025-12-24
CVE-2025-33222 NVIDIA Isaac Launchable 信任管理问题漏洞 — Isaac Launchable 9.8 Critical 2025-12-23
CVE-2025-7358 Use of Hard-coded Credentials in Utarit Informatics' SoliClub — SoliClub 7.5 High 2025-12-18
CVE-2025-1029 Hardcoded Credentials in Utarit Informatics' SoliClub — SoliClub 7.5 High 2025-12-18
CVE-2025-14096 Credential Disclosure vulnerability in Radiometer Products — ABL90 FLEX and ABL90 FLEX PLUS Analyzers 8.4 High 2025-12-17
CVE-2025-36747 Hardcoded FTP Credentials within the firmware — ShineLan-X 9.8AI Critical AI 2025-12-13
CVE-2025-36752 Undocumented backup Account and No Password Configuration Capability — ShineLan-X 9.8AI Critical AI 2025-12-13
CVE-2025-13954 Hard-coded cryptographic keys in EZCast Pro II Dongle — EZCast Pro II 9.8AI Critical AI 2025-12-10
CVE-2025-40938 Siemens SIMATIC CN 4100 信任管理问题漏洞 — SIMATIC CN 4100 8.1 High 2025-12-09
CVE-2025-41696 Hardcoded User Password — FL SWITCH 2005 4.6 Medium 2025-12-09
CVE-2025-14126 TOZED ZLT M30S/ZLT M30S PRO Web hard-coded credentials — ZLT M30S 8.8 High 2025-12-06
CVE-2025-66237 Sunbird DCIM dcTrack and Power IQ Use of Hard-coded Credentials — DCIM dcTrack 6.7 Medium 2025-12-04
CVE-2025-64778 Mirion Medical EC2 Software NMIS BioDose Use of Hard-coded Credentials — EC2 Software NMIS BioDose 7.3 High 2025-12-02
CVE-2018-25126 TVT NVMS-9000 Hard-coded API Credentials & Command Injection — NVMS-9000 9.8AI Critical AI 2025-11-24
CVE-2025-59669 Fortinet FortiWeb 信任管理问题漏洞 — FortiWeb 4.8 Medium 2025-11-18
CVE-2025-64766 NixOS has hardcoded credentials in Onlyoffice module — nixpkgs 5.3 Medium 2025-11-17
CVE-2025-13252 shsuishang ShopSuite ModulithShop RSA/OAuth2/Database hard-coded credentials — ShopSuite ModulithShop 7.3 High 2025-11-16
CVE-2025-33186 NVIDIA AIStore 信任管理问题漏洞 — AuthN component of NVIDIA AIStore 8.8 High 2025-11-11
CVE-2025-42890 Insecure key & Secret Management vulnerability in SQL Anywhere Monitor (Non-Gui) — SQL Anywhere Monitor (Non-Gui) 10.0 Critical 2025-11-11
CVE-2025-34501 Shuffle Master Deck Mate 2 Hard-coded Credentials & Exposed Services — Deck Mate 2 7.0 High 2025-11-03
CVE-2025-62777 Planex MZK-DP300N 信任管理问题漏洞 — MZK-DP300N 8.0AI High AI 2025-10-28
CVE-2025-41109 Use of Hard-coded Credentials vulnerability in Ghost Robotics' Vision 60 — Vision 60 4.6AI Medium AI 2025-10-22
CVE-2025-41722 Sauter: Hard-coded Authentication Credentials — modulo 6 devices modu680-AS 7.5 High 2025-10-22
CVE-2025-10639 Usage of Hardcoded FTP Credentials EfficientLab WorkExaminer Professional — WorkExaminer Professional 9.8AI Critical AI 2025-10-21
CVE-2025-6950 Moxa多款产品 安全漏洞 — EDR-G9010 Series 9.8AI Critical AI 2025-10-17
CVE-2025-10850 Felan Framework <= 1.1.4 - Hardcoded Credentials — Felan Framework 9.8 Critical 2025-10-16
CVE-2025-36087 IBM Security Verify Access hard coded credentials — Security Verify Access 8.1 High 2025-10-13

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