導入モード
Architecture and Design
Implementation : REALIZATION: This weakness is caused during implementation of an architectural security tactic.
適用可能なプラットフォーム
言語
クラス: Not Language-Specific (Undetermined)
一般的な結果
| スコープ |
影響 |
可能性 |
| Availability | DoS: Crash, Exit, or Restart
注記:A program may crash or block if it runs out of random numbers. | |
潜在的な緩和策
Phases : Implementation
Since the rate at which true random numbers can be generated is limited, it is important that one uses them only when they are needed for security.
Phases : Implementation
Rather than failing on a lack of random numbers, it is often preferable to wait for more numbers to be created.
脆弱性マッピングノート
理由 : 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.
ノート
As of CWE 4.5, terminology related to randomness, entropy, and
predictability can vary widely. Within the developer and other
communities, "randomness" is used heavily. However, within
cryptography, "entropy" is distinct, typically implied as a
measurement. There are no commonly-used definitions, even within
standards documents and cryptography papers. Future versions of
CWE will attempt to define these terms and, if necessary,
distinguish between them in ways that are appropriate for
different communities but do not reduce the usability of CWE for
mapping, understanding, or other scenarios.
参考文献
REF-18
The CLASP Application Security Process
Secure Software, Inc..
https://cwe.mitre.org/documents/sources/TheCLASPApplicationSecurityProcess.pdf
登録情報
| 名前 |
組織 |
日付 |
リリース日 |
Version |
| CLASP |
|
2006-07-19 +00:00 |
2006-07-19 +00:00 |
Draft 3 |
変更履歴
| 名前 |
組織 |
日付 |
コメント |
| Eric Dalci |
Cigital |
2008-07-01 +00:00 |
updated Time_of_Introduction |
| CWE Content Team |
MITRE |
2008-09-08 +00:00 |
updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2009-05-27 +00:00 |
updated Description, Name |
| CWE Content Team |
MITRE |
2009-10-29 +00:00 |
updated Description, Other_Notes |
| CWE Content Team |
MITRE |
2011-06-01 +00:00 |
updated Common_Consequences, Relationships, Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2012-05-11 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2012-10-30 +00:00 |
updated Demonstrative_Examples |
| CWE Content Team |
MITRE |
2017-11-08 +00:00 |
updated Applicable_Platforms, Likelihood_of_Exploit, Modes_of_Introduction, Relationships |
| CWE Content Team |
MITRE |
2019-01-03 +00:00 |
updated Taxonomy_Mappings |
| CWE Content Team |
MITRE |
2020-02-24 +00:00 |
updated References, Relationships |
| CWE Content Team |
MITRE |
2021-07-20 +00:00 |
updated Maintenance_Notes |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2024-02-29 +00:00 |
updated Relationships |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Description, Potential_Mitigations |