背景の詳細
導入モード
Implementation
適用可能なプラットフォーム
言語
クラス: Not Language-Specific (Undetermined)
一般的な結果
| スコープ |
影響 |
可能性 |
| Confidentiality | Read Application Data
注記:If the IV is not properly
initialized, the cryptography may be
weakened or broken by attacking the IVs
themselves. Data that is encrypted can be
compromised, and information about the data
can be leaked. See [REF-1179]. | |
観察された例
| 参考文献 |
説明 |
| ZeroLogon vulnerability - use of a static IV of all zeroes in AES-CFB8 mode |
| BEAST attack in SSL 3.0 / TLS 1.0. In CBC mode, chained initialization vectors are non-random, allowing decryption of HTTPS traffic using a chosen plaintext attack. |
| wireless router does not use 6 of the 24 bits for WEP encryption, making it easier for attackers to decrypt traffic |
| WEP card generates predictable IV values, making it easier for attackers to decrypt traffic |
| device bootloader uses a zero initialization vector during AES-CBC |
| crypto framework uses PHP rand function - which is not cryptographically secure - for an initialization vector |
| encryption routine does not seed the random number generator, causing the same initialization vector to be generated repeatedly |
| encryption functionality in an authentication framework uses a fixed null IV with CBC mode, allowing attackers to decrypt traffic in applications that use this functionality |
| messages for a door-unlocking product use a fixed IV in CBC mode, which is the same after each restart |
| application uses AES in CBC mode, but the pseudo-random secret and IV are generated using math.random, which is not cryptographically strong. |
| Blowfish-CBC implementation constructs an IV where each byte is calculated modulo 8 instead of modulo 256, resulting in less than 12 bits for the effective IV length, and less than 4096 possible IV values. |
潜在的な緩和策
Phases : Implementation
検出方法
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 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.
関連する攻撃パターン
| CAPEC ID |
攻撃パターン名 |
| CAPEC-20 |
Encryption Brute Forcing
An attacker, armed with the cipher text and the encryption algorithm used, performs an exhaustive (brute force) search on the key space to determine the key that decrypts the cipher text to obtain the plaintext. |
| CAPEC-97 |
Cryptanalysis
Cryptanalysis is a process of finding weaknesses in cryptographic algorithms and using these weaknesses to decipher the ciphertext without knowing the secret key (instance deduction). Sometimes the weakness is not in the cryptographic algorithm itself, but rather in how it is applied that makes cryptanalysis successful. An attacker may have other goals as well, such as: Total Break (finding the secret key), Global Deduction (finding a functionally equivalent algorithm for encryption and decryption that does not require knowledge of the secret key), Information Deduction (gaining some information about plaintexts or ciphertexts that was not previously known) and Distinguishing Algorithm (the attacker has the ability to distinguish the output of the encryption (ciphertext) from a random permutation of bits). |
ノート
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-1175
Intercepting Mobile Communications: The Insecurity of 802.11
Nikita Borisov, Ian Goldberg, David Wagner.
http://www.isaac.cs.berkeley.edu/isaac/mobicom.pdf REF-1175
Intercepting Mobile Communications: The Insecurity of 802.11
Nikita Borisov, Ian Goldberg, David Wagner.
http://www.isaac.cs.berkeley.edu/isaac/mobicom.pdf REF-1176
Birthday problem
Wikipedia.
https://en.wikipedia.org/wiki/Birthday_problem REF-1177
Initialization Vector
Wikipedia.
https://en.wikipedia.org/wiki/Initialization_vector REF-1178
Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC
NIST.
https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf REF-1179
CBC Mode is Malleable. Don't trust it for Authentication
Arxum Path Security.
https://arxumpathsecurity.com/blog/2019/10/16/cbc-mode-is-malleable-dont-trust-it-for-authentication
登録情報
| 名前 |
組織 |
日付 |
リリース日 |
Version |
| CWE Content Team |
MITRE |
2021-03-09 +00:00 |
2021-03-15 +00:00 |
4.4 |
変更履歴
| 名前 |
組織 |
日付 |
コメント |
| CWE Content Team |
MITRE |
2021-07-20 +00:00 |
updated Maintenance_Notes, Observed_Examples, References |
| CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated References, Relationships, Time_of_Introduction |
| CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
| CWE Content Team |
MITRE |
2025-12-11 +00:00 |
updated Detection_Factors, Weakness_Ordinalities |
| CWE Content Team |
MITRE |
2026-10-28 +00:00 |
updated Background_Details, Common_Consequences, Description |