CWE-474 상세 정보

The code uses a function that has inconsistent implementations across operating systems and versions.

취약점 도입 방식

Implementation

적용 가능한 플랫폼

언어

이름: C (Often)
이름: PHP (Often)
클래스: Not Language-Specific (Undetermined)

일반적인 결과

잠재적 완화 방법

Phases : Architecture and Design // Requirements
Do not accept inconsistent behavior from the API specifications when the deviant behavior increases the risk level.

탐지 방법

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.

참고 자료

REF-6

Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors
Katrina Tsipenyuk, Brian Chess, Gary McGraw.
https://cwe.mitre.org/documents/sources/SevenPerniciousKingdoms.pdf

제출

수정 사항