名称: Use of Hard-coded Cryptographic Key
The product uses a hard-coded, unchangeable cryptographic key.
基本信息
引入方式
Architecture and Design : REALIZATION: This weakness is caused during implementation of an architectural security tactic.适用平台
编程语言
类： Not Language-Specific (Undetermined)名称： Go (Undetermined)
技术
类： ICS/OT (Undetermined)常见后果
| 影响范围 | 影响 | 可能性 |
|---|---|---|
| Access Control | Bypass Protection Mechanism, Gain Privileges or Assume Identity, Read Application Data 注意： If hard-coded cryptographic keys are used, it is almost certain that malicious users will gain access through the account in question. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. |
观察示例
| 参考资料 | 描述 |
|---|---|
CVE-2022-29960 | Engineering Workstation uses hard-coded cryptographic keys that could allow for unauthorized filesystem access and privilege escalation |
CVE-2022-30271 | Remote Terminal Unit (RTU) uses a hard-coded SSH private key that is likely to be used in typical deployments. |
CVE-2020-10884 | WiFi router service has a hard-coded encryption key, allowing root access |
CVE-2014-2198 | Communications / collaboration product has a hardcoded SSH private key, allowing access to root account |
潜在缓解措施
Phases : Architecture and DesignPrevention schemes mirror that of hard-coded password storage.
检测方法
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)有效性 : High
漏洞映射说明
依据 : This CWE entry is at the Variant 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.
备注
The main difference between the use of hard-coded passwords and the use of hard-coded cryptographic keys is the false sense of security that the former conveys. Many people believe that simply hashing a hard-coded password before storage will protect the information from malicious users. However, many hashes are reversible (or at least vulnerable to brute force attacks) -- and further, many authentication protocols simply request the hash itself, making it no better than a password.参考资料
REF-18
The CLASP Application Security ProcessSecure Software, Inc..
https://cwe.mitre.org/documents/sources/TheCLASPApplicationSecurityProcess.pdf
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/
REF-1534
Automated Technical Debt Measure, Version 2OMG.
https://www.omg.org/spec/ATDM2/1.0/PDF
REF-1566
Golang Secure Coding Practices guideOWASP.
https://github.com/OWASP/Go-SCP
提交记录
| 名称 | 组织 | 日期 | 发布日期 | Version |
|---|---|---|---|---|
| CLASP | Draft 3 |
修改记录
| 名称 | 组织 | 日期 | 备注 |
|---|---|---|---|
| Eric Dalci | Cigital | updated Time_of_Introduction | |
| Veracode | Suggested OWASP Top Ten 2004 mapping | ||
| CWE Content Team | MITRE | updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Demonstrative_Examples | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Common_Consequences | |
| CWE Content Team | MITRE | updated Demonstrative_Examples, Relationships | |
| CWE Content Team | MITRE | updated Demonstrative_Examples, Relationships, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Demonstrative_Examples, Modes_of_Introduction, Relationships | |
| CWE Content Team | MITRE | updated References, Relationships, Type | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Demonstrative_Examples, Observed_Examples, References | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Maintenance_Notes, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Detection_Factors, Relationships, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Mapping_Notes, Taxonomy_Mappings | |
| CWE Content Team | MITRE | updated Common_Consequences, Description, Diagram | |
| CWE Content Team | MITRE | updated Maintenance_Notes, Relationships, Weakness_Ordinalities | |
| CWE Content Team | MITRE | updated Applicable_Platforms, Observed_Examples, References, Relationships, Taxonomy_Mappings |
