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

제출

수정 사항