COMMON WEAKNESS ENUMERATIONIncomplete

CWE-192

Integer Coercion Error

Integer coercion refers to a set of flaws pertaining to the type casting, extension, or truncation of primitive data types.

Soyutlama

Variant

Yapı

Simple

Sömürü İhtimali

Medium

Problemi anla

Problem nedir?

Integer coercion refers to a set of flaws pertaining to the type casting, extension, or truncation of primitive data types.

Genişletilmiş açıklama

Several flaws fall under the category of integer coercion errors. For the most part, these errors in and of themselves result only in availability and data integrity issues. However, in some circumstances, they may result in other, more complicated security related flaws, such as buffer overflow conditions.

Kök neden

Problem nasıl ve ne zaman oluşur?

Yaşam döngüsü evresi

Implementation

Risk

Başarılı sömürü neye yol açar?

DoS: Resource Consumption (CPU)DoS: Resource Consumption (Memory)DoS: Crash, Exit, or Restart

Etkilenen güvenlik alanları: Availability

Integer coercion often leads to undefined states of execution resulting in infinite loops or crashes.
Execute Unauthorized Code or Commands

Etkilenen güvenlik alanları: Integrity, Confidentiality, Availability

In some cases, integer coercion errors can lead to exploitable buffer overflow conditions, resulting in the execution of arbitrary code.
Other

Etkilenen güvenlik alanları: Integrity, Other

Integer coercion errors result in an incorrect value being stored for the variable in question.

Savunma

Nasıl önlenir ve çözülür?

Requirements

Güvenlik gereksinimi

Detay
A language which throws exceptions on ambiguous data casts might be chosen.

Architecture and Design

Mimari ve tasarım yaklaşımı

Detay
Design objects and program flow such that multiple or complex casts are unnecessary

Implementation

Uygulama aşaması savunması

Detay
Ensure that any data type casting that you must used is entirely understood in order to reduce the plausibility of error in use.

Doğrulama

Nasıl tespit edilir?

Automated Static Analysis

High
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.)