名稱: Use of Default Credentials
The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.
一般資訊
引入方式
Array : It is common practice for products to be designed to use default keys, passwords, or other mechanisms for authentication. The rationale is to simplify the manufacturing process or the system administrator's task of installation and deployment into an enterprise. However, this places the responsibility of changing defaults onto the administrator.適用平台
程式語言
類別： Not Language-Specific (Undetermined)作業系統
類別： Not OS-Specific (Undetermined)架構
類別： Not Architecture-Specific (Undetermined)技術
類別： ICS/OT (Undetermined)類別： Not Technology-Specific (Undetermined)
常見後果
| 範圍 | 影響 | 可能性 |
|---|---|---|
| Authentication | Gain Privileges or Assume Identity 注意：If admins do not change the defaults, it is easier for attackers to bypass authentication quickly across multiple organizations. |
觀察到的案例
| 參考資料 | 描述 |
|---|---|
CVE-2022-30270 | Remote Terminal Unit (RTU) uses default credentials for some SSH accounts |
CVE-2021-41192 | data visualization/sharing package uses default secret keys or cookie values if they are not specified in environment variables |
CVE-2021-38759 | microcontroller board has default password, allowing admin access |
CVE-2018-3825 | cloud cluster management product has a default master encryption key |
CVE-2010-2306 | Intrusion Detection System (IDS) uses the same static, private SSL keys for multiple devices and installations, allowing decryption of SSL traffic |
潛在緩解措施
Phases : RequirementsProhibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.
Phases : Architecture and Design
Force the administrator to change the credential upon installation.
Phases : Installation // Operation
The product administrator could change the defaults upon installation or during operation.
漏洞對應備注
理由說明 : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.備註 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
參考資料
REF-1283
OT:ICEFALL: The legacy of "insecure by design" and its implications for certifications and risk managementForescout Vedere Labs.
https://www.forescout.com/resources/ot-icefall-report/
提交
| 名稱 | 機構 | 日期 | 發布日期 | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 4.9 |
修改記錄
| 名稱 | 機構 | 日期 | 備註 |
|---|---|---|---|
| CWE Content Team | MITRE | updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, References | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes | |
| CWE Content Team | MITRE | updated Observed_Examples | |
| CWE Content Team | MITRE | updated Observed_Examples, Relationships, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Common_Consequences, Description, Modes_of_Introduction, Time_of_Introduction |
