目标达成 感谢每一位支持者 — 我们达成了 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-2020-25168 B. Braun Melsungen Ag B. Braun Melsungen AG SpaceCom 信任管理问题漏洞 — SpaceCom 3.3 Low 2022-04-14
CVE-2021-40422 Swift Sensors Gateway SG3-1010 信任管理问题漏洞 — Swift Sensors Gateway 10.0 Critical 2022-04-14
CVE-2021-40390 MOXA Moxa MXView 信任管理问题漏洞 — MXView Series 9.8 - 2022-04-14
CVE-2022-27506 Citrix SD-WAN 信任管理问题漏洞 — Citrix SD-WAN 6.7 - 2022-04-13
CVE-2022-22560 Dell Technologies Dell PowerScale OneFS 信任管理问题漏洞 — PowerScale OneFS 7.1 High 2022-04-12
CVE-2022-26671 Taiwan Secom Dr.ID Access control 信任管理问题漏洞 — Personnel Attendance Management system 7.3 High 2022-04-07
CVE-2021-27430 GE Grid Solutions UR 信任管理问题漏洞 — UR bootloader binary 8.4 High 2022-03-23
CVE-2022-25246 PTC Axeda agent 信任管理问题漏洞 — Axeda agent 9.8 Critical 2022-03-16
CVE-2022-23402 Yokogawa Electric 信任管理问题漏洞 — CENTUM VP 8.8 - 2022-03-11
CVE-2022-21194 Yokogawa Electric 信任管理问题漏洞 — CENTUM VP 8.8 - 2022-03-11
CVE-2022-22765 BD Viper LT 信任管理问题漏洞 — BD Viper LT System 8.0 High 2022-02-12
CVE-2022-22766 BD Pyxis 信任管理问题漏洞 — BD Pyxis Anesthesia Station ES 7.0 High 2022-02-11
CVE-2022-22813 Schneider Electric Easergy P40 信任管理问题漏洞 — Easergy P40 Series model numbers with Ethernet option bit as Q, R, S (All PX4X firmware Versions) 8.1 - 2022-02-09
CVE-2021-45106 Siemens Sicam Toolbox II 信任管理问题漏洞 — SICAM TOOLBOX II 6.5 - 2022-02-09
CVE-2022-22722 Schneider Electric Easergy P5 信任管理问题漏洞 — Easergy P5 7.4 - 2022-02-04
CVE-2021-44464 Fresenius Kabi Agilia Connect Infusion System 信任管理问题漏洞 — Vigilant Software Suite (Mastermed Dashboard) 6.3 Medium 2022-01-21
CVE-2022-22056 Le-Yan Dental Management System 信任管理问题漏洞 — Dental Management System 9.8 Critical 2022-01-14
CVE-2021-45033 Siemens SICAM A8000 CP-8000 信任管理问题漏洞 — CP-8000 MASTER MODULE WITH I/O -25/+70°C 8.8 - 2022-01-11
CVE-2022-21669 Pudding-Bot 信任管理问题漏洞 — pudding-bot 9.1 Critical 2022-01-11
CVE-2021-45458 Apache Kylin 安全特征问题漏洞 — Apache Kylin 7.5 - 2022-01-06
CVE-2021-32993 Philips IntelliBridge EC80 Hub 信任管理问题漏洞 — IntelliBridge EC 40 Hub 8.1 High 2021-12-27
CVE-2021-35232 Solarwinds Web Help Desk 信任管理问题漏洞 — Web Help Desk 6.8 Medium 2021-12-27
CVE-2021-26611 HejHome Gkw-Ic052 信任管理问题漏洞 — GKW-IC052 8.1 High 2021-11-26
CVE-2021-41299 Ecoa Bas controller 信任管理问题漏洞 — ECS Router Controller ECS (FLASH) 9.8 Critical 2021-09-30
CVE-2021-21913 D-LINK DIR-3040 信任管理问题漏洞 — D-Link 9.8 - 2021-09-23
CVE-2021-34571 Enbra Ewm信任管理问题漏洞 — AT-WMBUS-16-2 6.5 Medium 2021-09-16
CVE-2021-34565 Pepperl Fuchs WirelessHART-Gateway 信任管理问题漏洞 — WHA-GW-F2D2-0-AS- Z2-ETH 9.8 Critical 2021-08-31
CVE-2021-27503 Ypsomed mylife App 信任管理问题漏洞 — Ypsomed mylife Cloud, mylife Mobile Application 6.5 - 2021-08-02
CVE-2021-31579 Akkadian Provisioning Manager 信任管理问题漏洞 — Provisioning Manager Engine (PME) 8.2 High 2021-07-22
CVE-2021-22730 EVlink City、EVlink Parking、EVlink Smart Wallbox 信任管理问题漏洞 — EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink Parking (EVW2 / EVF2 / EV.2 all versions prior to R8 V3.4.0.1), and EVlink Smart Wallbox (EVB1A all versions prior to R8 V3.4.0.1 ) 9.8 - 2021-07-21

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