目标达成 感谢每一位支持者 — 我们达成了 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-2026-58245 SAP Advanced Planning and Optimization 信任管理问题漏洞 — SAP Advanced Planning and Optimization (Model Mix Planning) 3.8 Low 2026-08-11
CVE-2025-13293 TBEA TLogger 信任管理问题漏洞 — TBEA TLogger (TBEA Communication Box 3rd Generation) 9.3 Critical 2026-08-10
CVE-2026-6374 Zyxel WAH7601 信任管理问题漏洞 — WAH7601 7.3 High 2026-08-10
CVE-2026-49007 ZTE F689 信任管理问题漏洞 — F689 7.5 High 2026-08-07
CVE-2026-71238 VadKhar Django-CRM 信任管理问题漏洞 — django-crm 9.1 Critical 2026-08-05
CVE-2026-48031 dhax Go Restful API Boilerplate 信任管理问题漏洞 — go-base 9.1 Critical 2026-08-03
CVE-2025-15628 TP-Link Omada 信任管理问题漏洞 — Omada Gateways 8.2 High 2026-08-03
CVE-2026-65313 ANDRITZ HIPASE-250 信任管理问题漏洞 — HIPASE-250 8.1 High 2026-07-31
CVE-2026-18452 DMS+（非移动端）硬编码凭证漏洞 — DMS+ (Non-Mobile) 10.0 Critical 2026-07-31
CVE-2026-13463 IBM Cloud Pak System 信任管理问题漏洞 — Cloud Pak System 7.5 High 2026-07-28
CVE-2026-12001 TP-Link TL-WR845N 信任管理问题漏洞 — TL-WR850N v3 5.2 Medium 2026-07-27
CVE-2026-55579 Pheditor 默认密码未强制修改致应用被控 — pheditor 9.8 Critical 2026-07-27
CVE-2025-59180 Ericsson Packet Core Controller 信任管理问题漏洞 — Packet Core Controller (PCC) 5.1 Medium 2026-07-27
CVE-2026-8983 Autel MaxiCharger Single 信任管理问题漏洞 — MaxiCharger Single - - 2026-07-21
CVE-2026-8982 Autel MaxiCharger Single 信任管理问题漏洞 — MaxiCharger Single - - 2026-07-21
CVE-2026-13446 IBM Langflow OSS 信任管理问题漏洞 — Langflow OSS 9.8 Critical 2026-07-17
CVE-2026-45336 StratonWebDesigners HireFlow 信任管理问题漏洞 — HireFlow 10.0 Critical 2026-07-16
CVE-2026-49352 decolua 9router 信任管理问题漏洞 — 9router 9.8 Critical 2026-07-15
CVE-2026-61684 labring FastGPT 信任管理问题漏洞 — FastGPT - - 2026-07-15
CVE-2026-14807 BorG ERP APP 信任管理问题漏洞 — ERP App 9.8 Critical 2026-07-06
CVE-2026-13768 Gardyn Cloud API 信任管理问题漏洞 — Gardyn Home Firmware 10.0 Critical 2026-07-02
CVE-2026-13728 WatchGuard Fireware OS 信任管理问题漏洞 — Fireware OS 5.9 Medium 2026-07-02
CVE-2026-7839 UltraVNC 信任管理问题漏洞 — UltraVNC 9.1 Critical 2026-07-01
CVE-2026-50110 StoneFly Storage Concentrator 信任管理问题漏洞 — Storage Concentrator 9.2 Critical 2026-06-30
CVE-2026-56278 FlowiseAI Flowise 信任管理问题漏洞 — Flowise 9.1 Critical 2026-06-30
CVE-2026-31928 Daktronics VFC-DMP-5000 信任管理问题漏洞 — VFC-DMP-5000 8.1 High 2026-06-26
CVE-2026-56269 FlowiseAI Flowise 信任管理问题漏洞 — Flowise 4.6 Medium 2026-06-24
CVE-2026-12628 IBM Storage Protect Client 信任管理问题漏洞 — Storage Protect Client 9.1 Critical 2026-06-22
CVE-2026-56265 UncleCode Crawl4AI 信任管理问题漏洞 — Crawl4AI 9.8 Critical 2026-06-21
CVE-2026-47846 Bitnami Cassandra 信任管理问题漏洞 — bitnami/cassandra 9.8 Critical 2026-06-18

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