CWE-1043 상세 정보

The product uses a data element that has an excessively large number of sub-elements with non-primitive data types such as structures or aggregated objects.

취약점 도입 방식

Implementation

적용 가능한 플랫폼

언어

클래스: 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 entry is primarily a quality issue with no direct security implications.
댓글 : Look for weaknesses that are focused specifically on insecure behaviors that have more direct security implications.

메모

While the interpretation of "excessively large" may vary for each product or developer, CISQ recommends a default of 5 sub-elements. [REF-1133]

참고 자료

REF-959

Automated Source Code Performance Efficiency Measure (ASCPEM)
Object Management Group (OMG).
https://www.omg.org/spec/ASCPEM/

REF-1534

Automated Technical Debt Measure, Version 2
OMG.
https://www.omg.org/spec/ATDM2/1.0/PDF

REF-1133

Automated Source Code Quality Measures
Consortium for Information & Software Quality (CISQ).
https://www.omg.org/spec/ASCQM/

제출

수정 사항