目标达成 感谢每一位支持者 — 我们达成了 100% 目标！

目标: 1000 元 · 已筹: 1336 元

100%
请我们喝杯咖啡

CWE-798 使用硬编码的凭证 类漏洞列表 684

CWE-798 使用硬编码的凭证 类弱点 684 条 CVE 漏洞汇总，含 AI 中文分析。

CWE-798指硬编码凭据漏洞，即软件将密码或密钥直接写入代码。攻击者可通过逆向工程提取这些固定凭据，从而绕过认证机制获取未授权访问权限。为避免此类风险，开发者应严禁在代码中硬编码敏感信息，转而采用环境变量、密钥管理系统或配置数据库等动态方式存储凭据，确保凭据与代码分离，提升系统安全性。

MITRE CWE 官方描述
CWE：CWE-798 使用硬编码凭证 (Use of Hard-coded Credentials) 英文：该产品包含硬编码凭证 (hard-coded credentials)，例如密码 (password) 或加密密钥 (cryptographic key)。 主要有两种变体： 入站 (Inbound)：该产品包含一种身份验证机制，将输入的凭证 (input credentials) 与一组硬编码凭证 (hard-coded set of credentials) 进行比对。在此变体中，会创建一个默认的管理员账户 (default administration account)，并将一个简单的密码 (simple password) 硬编码到产品中并与该账户关联。此硬编码密码 (hard-coded password) 在产品的每次安装中都是相同的，并且通常无法由系统管理员 (system administrators) 在不手动修改程序或修补产品的情况下更改或禁用。管理员也难以检测到此问题。 出站 (Outbound)：该产品连接到另一个系统或组件，并包含用于连接该组件的硬编码凭证 (hard-coded credentials)。此变体适用于与后端服务 (back-end service) 进行身份验证的前端系统 (front-end systems)。后端服务 (back-end service) 可能需要一个容易被发现的固定密码 (fixed password)。程序员可能只是将这些后端凭证 (back-end credentials) 硬编码到前端产品 (front-end product) 中。
常见影响 (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…
缓解措施 (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…
代码示例 (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 标题 CVSS 风险等级 Published
CVE-2025-1393 Weidmueller Interface PROCON-WIN 信任管理问题漏洞 — PROCON-WIN 9.8 Critical 2025-03-05
CVE-2025-1879 i-Drive i11和i-Drive i12 安全漏洞 — i11 2.4 Low 2025-03-03
CVE-2024-9334 E-Kent Pallium Vehicle Tracking 安全漏洞 — Pallium Vehicle Tracking 8.2 High 2025-02-27
CVE-2024-52902 IBM Cognos Controller 信任管理问题漏洞 — Cognos Controller 8.8 High 2025-02-19
CVE-2024-8893 GoodWe GW1500-XS 安全漏洞 — GW1500‑XS 7.3 High 2025-02-14
CVE-2025-26410 Wattsense Bridge 安全漏洞 — Wattsense Bridge 9.8 - 2025-02-11
CVE-2025-1143 Billion Electric M100、M150和M120N 信任管理问题漏洞 — M100 8.4 High 2025-02-11
CVE-2024-51547 ABB多款产品 信任管理问题漏洞 — ASPECT-Enterprise 9.8 Critical 2025-02-06
CVE-2024-55927 Xerox Workplace Suite 信任管理问题漏洞 — Xerox Workplace Suite 7.6 High 2025-01-23
CVE-2024-11147 ECOVACS robot lawnmowers和vacuums 信任管理问题漏洞 — Unspecified robots 7.6 High 2025-01-23
CVE-2024-45832 Ossur Mobile Logic Application 信任管理问题漏洞 — Mobile Logic Application 4.3 Medium 2025-01-17
CVE-2024-28778 IBM Cognos Controller和IBM Controller 信任管理问题漏洞 — Controller 6.5 Medium 2025-01-07
CVE-2024-28146 Image Access Scan2Net 安全漏洞 — Scan2Net 9.8 - 2024-12-12
CVE-2024-45319 SonicWALL SMA100 安全漏洞 — SMA100 6.5 - 2024-12-05
CVE-2024-41777 IBM Cognos Controller 信任管理问题漏洞 — Cognos Controller 7.5 High 2024-12-03
CVE-2024-49806 IBM Security Verify Access 信任管理问题漏洞 — Security Verify Access 9.4 Critical 2024-11-29
CVE-2024-49805 IBM Security Verify Access 信任管理问题漏洞 — Security Verify Access 9.4 Critical 2024-11-29
CVE-2024-36248 Sharp MFP 安全漏洞 — Multiple MFPs (multifunction printers) 9.1 Critical 2024-11-26
CVE-2024-35244 Sharp MFP 安全漏洞 — Multiple MFPs (multifunction printers) 9.1 Critical 2024-11-26
CVE-2024-10451 Red Hat Keycloak 安全漏洞 — Red Hat build of Keycloak 24 5.9 Medium 2024-11-25
CVE-2024-11630 E-Lins多款产品 安全漏洞 — H685 7.3 High 2024-11-22
CVE-2023-51638 Allegra 信任管理问题漏洞 — Allegra 9.8 - 2024-11-22
CVE-2024-49060 Microsoft Azure Stack HCI 信任管理问题漏洞 — Azure Stack HCI OS 8.8 High 2024-11-15
CVE-2024-48971 Baxter Life2000 信任管理问题漏洞 — Life2000 Ventilation System 9.3 Critical 2024-11-14
CVE-2024-52295 DataEase 信任管理问题漏洞 — dataease 9.8AI Critical AI 2024-11-13
CVE-2024-7295 Progress Telerik Report Server 信任管理问题漏洞 — Telerik Report Server 7.1 High 2024-11-13
CVE-2024-50593 HASOMED Elefant 安全漏洞 — Elefant 6.7 - 2024-11-08
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 信任管理问题漏洞 — Flexible Service Processor 9.8 Critical 2024-10-29

CWE-798（使用硬编码的凭证） 是常见的弱点类别，本平台收录该类弱点关联的 684 条 CVE 漏洞。