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

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

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

687 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-2024-28875 LevelOne WBR-6012 信任管理问题漏洞 — WBR-6012 8.1 High 2024-10-30
CVE-2024-31151 LevelOne WBR-6012 信任管理问题漏洞 — WBR-6012 8.1 High 2024-10-30
CVE-2024-45656 IBM Flexible Service Processor hard coded credentials — Flexible Service Processor 9.8 Critical 2024-10-29
CVE-2024-5764 Nexus Repository 3 - Static hard-coded encryption passphrase used by default — Nexus Repository 7.2AI High AI 2024-10-23
CVE-2024-4740 MXsecurity Use of Hard-coded Credentials — MXsecurity Series 5.3 Medium 2024-10-18
CVE-2024-10025 Vulnerability in SICK CLV6xx, SICK Lector6xx and SICK RFx6xx — SICK CLV6xx 9.1 Critical 2024-10-17
CVE-2024-9594 VM images built with Image Builder with some providers use default credentials during builds — Image Builder 6.3 Medium 2024-10-15
CVE-2024-9486 VM images built with Image Builder and Proxmox provider use default credentials — Image Builder 9.8 Critical 2024-10-15
CVE-2024-45275 MB connect line/Helmholz: Hardcoded user accounts with hard-coded passwords — mbNET.mini 9.8 Critical 2024-10-15
CVE-2024-8450 PLANET Technology switch devices - Hard-coded SNMPv1 read-write community string — GS-4210-24PL4C hardware 2.0 8.6 High 2024-09-30
CVE-2024-8449 PLANET Technology switch devices - Local users' passwords recovery through hard-coded credentials — GS-4210-24PL4C hardware 2.0 6.8 Medium 2024-09-30
CVE-2024-8448 PLANET Technology switch devices - Remote privilege escalation using hard-coded credentials — GS-4210-24PL4C hardware 2.0 8.8 High 2024-09-30
CVE-2024-23958 Autel MaxiCharger AC Elite Business C50 BLE Hardcoded Credentials Authentication Bypass Vulnerability — MaxiCharger AC Elite Business C50 6.5 Medium 2024-09-28
CVE-2024-45861 Use of Hard-coded Credentials in Kastle Systems Access Control System — Access Control System 9.8AI Critical AI 2024-09-19
CVE-2024-6656 Hardcoded Credentals in TNB Mobile Solutions' Cockpit Software — Cockpit Software 7.5AI High AI 2024-09-13
CVE-2024-28990 SolarWinds Access Rights Manager (ARM) Hardcoded Credentials Authentication Bypass Vulnerability — Access Rights Manager 6.3 Medium 2024-09-12
CVE-2024-39582 Dell InsightIQ 信任管理问题漏洞 — PowerScale InsightIQ 2.3 Low 2024-09-10
CVE-2024-35118 IBM MaaS360 information disclosure — MaaS360 4.6 Medium 2024-08-29
CVE-2024-8162 TOTOLINK T10 AC1200 Telnet Service product.ini hard-coded credentials — T10 AC1200 9.8 Critical 2024-08-26
CVE-2024-8135 Go-Tribe gotribe token.go Sign hard-coded credentials — gotribe 6.3 Medium 2024-08-24
CVE-2024-28987 SolarWinds Web Help Desk Hardcoded Credential Vulnerability — Web Help Desk 9.1 Critical 2024-08-21
CVE-2024-8005 demozx gf_cms JWT Authentication auth.go init hard-coded credentials — gf_cms 7.3 High 2024-08-20
CVE-2024-41161 Vonets WiFi Bridges Use of Hard-coded Credentials — VAR1200-H 7.5 High 2024-08-08
CVE-2024-41689 Hard-coded Credentials Vulnerability — SyroTech SY-GPON-1110-WDONT router 4.6 - 2024-07-26
CVE-2024-6912 Hardcoded MSSQL Credentials — ProcessPlus 9.8AI Critical AI 2024-07-22
CVE-2024-5471 Agent takeover — DDI Central 8.8 High 2024-07-17
CVE-2024-5810 WP2Speed Faster – Optimize PageSpeed Insights Score 90-100 <= 1.0.1 - Improper Authorization due to use of Hardcoded Credentials — WP2Speed Faster – Optimize PageSpeed Insights Score 90-100 5.3 Medium 2024-07-09
CVE-2024-28751 ifm: Hardcoded telnet credentials in Smart PLC — Smart PLC AC14xx Firmware 9.1 Critical 2024-07-09
CVE-2024-28747 ifm: Use of Hard-coded Credentials — Smart PLC AC14xx Firmware 9.8 Critical 2024-07-09
CVE-2023-41919 Use of Hard-coded Credentials in Kiloview P1/P2 devices — P1/P2 9.8 Critical 2024-07-02

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