目标达成 感谢每一位支持者 — 我们达成了 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-2022-50696 SOUND4多款产品 信任管理问题漏洞 — Impact/Pulse/First 9.8 Critical 2025-12-30
CVE-2025-68926 rustfs 信任管理问题漏洞 — rustfs 9.8 Critical 2025-12-30
CVE-2019-25241 iWT FaceSentry Access Control System 安全漏洞 — FaceSentry Access Control System 7.5 High 2025-12-24
CVE-2018-25138 FLIR AX8 Thermal Camera 安全漏洞 — 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 Utarit SoliClub 信任管理问题漏洞 — SoliClub 7.5 High 2025-12-18
CVE-2025-1029 Utarit SoliClub 信任管理问题漏洞 — SoliClub 7.5 High 2025-12-18
CVE-2025-14096 Radiometer Products 安全漏洞 — ABL90 FLEX and ABL90 FLEX PLUS Analyzers 8.4 High 2025-12-17
CVE-2025-36747 Growatt ShineLan-X 安全漏洞 — ShineLan-X 9.8AI Critical AI 2025-12-13
CVE-2025-36752 Growatt ShineLan-X 安全漏洞 — ShineLan-X 9.8AI Critical AI 2025-12-13
CVE-2025-13954 Ezcast EZCast Pro II 安全漏洞 — 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 Phoenix Contact FL SWITCH 信任管理问题漏洞 — FL SWITCH 2005 4.6 Medium 2025-12-09
CVE-2025-14126 TOZED ZLT M30S和TOZED ZLT M30S PRO 信任管理问题漏洞 — ZLT M30S 8.8 High 2025-12-06
CVE-2025-66237 Sunbird DCIM dcTrack 信任管理问题漏洞 — DCIM dcTrack 6.7 Medium 2025-12-04
CVE-2025-64778 Mirion Medical EC2 Software NMIS BioDose 信任管理问题漏洞 — EC2 Software NMIS BioDose 7.3 High 2025-12-02
CVE-2018-25126 TVT NVMS-9000 安全漏洞 — NVMS-9000 9.8AI Critical AI 2025-11-24
CVE-2025-59669 Fortinet FortiWeb 信任管理问题漏洞 — FortiWeb 4.8 Medium 2025-11-18
CVE-2025-64766 ONLYOFFICE Docs 信任管理问题漏洞 — nixpkgs 5.3 Medium 2025-11-17
CVE-2025-13252 ModulithShop 信任管理问题漏洞 — 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 SAP SQL Anywhere 信任管理问题漏洞 — SQL Anywhere Monitor (Non-Gui) 10.0 Critical 2025-11-11
CVE-2025-34501 Light & Wonder Deck Mate 安全漏洞 — 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 Ghost Robotics Vision 60 信任管理问题漏洞 — Vision 60 4.6AI Medium AI 2025-10-22
CVE-2025-41722 Sauter modu680-AS 信任管理问题漏洞 — modulo 6 devices modu680-AS 7.5 High 2025-10-22
CVE-2025-10639 Work Examiner 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 WordPress plugin Felan Framework 信任管理问题漏洞 — Felan Framework 9.8 Critical 2025-10-16
CVE-2025-36087 IBM Security Verify Access（ISAM）和IBM Verify Identity Access Container 信任管理问题漏洞 — Security Verify Access 8.1 High 2025-10-13

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