CWE-780 詳細

The product uses the RSA algorithm but does not incorporate Optimal Asymmetric Encryption Padding (OAEP).

背景の詳細

導入モード

Implementation : REALIZATION: This weakness is caused during implementation of an architectural security tactic.

適用可能なプラットフォーム

言語

クラス： Not Language-Specific (Undetermined)

一般的な結果

検出方法

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.

ノート

This entry could probably have a new parent related to improper padding, however the role of padding in cryptographic algorithms can vary, such as hiding the length of the plaintext and providing additional random bits for the cipher. In general, cryptographic problems in CWE are not well organized and further research is needed.

参考文献

REF-694

RSA Problem
Ronald L. Rivest, Burt Kaliski.
https://people.csail.mit.edu/rivest/pubs/RK03.prepub.pdf

REF-695

Optimal Asymmetric Encryption Padding
https://en.wikipedia.org/wiki/Optimal_asymmetric_encryption_padding

登録情報

変更履歴