Umbra Wiki weakness weakness/CWE-682
Back to wiki

CWE-682 — Incorrect Calculation

provenance: imported · CWE: CWE-682

CWE-682: Incorrect Calculation

MITRE CWE weakness

Kind Weakness
Abstraction Pillar
Status Draft
Likelihood of exploit High

Description

The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.

When product performs a security-critical calculation incorrectly, it might lead to incorrect resource allocations, incorrect privilege assignments, or failed comparisons among other things. Many of the direct results of an incorrect calculation can lead to even larger problems such as failed protection mechanisms or even arbitrary code execution.

Common consequences

  • Availability: DoS: Crash, Exit, or Restart
  • Integrity, Confidentiality, Availability: DoS: Crash, Exit, or Restart, DoS: Resource Consumption (Other), Execute Unauthorized Code or Commands
  • Access Control: Gain Privileges or Assume Identity
  • Access Control: Bypass Protection Mechanism

Mitigations

Implementation — Understand your programming language's underlying representation and how it interacts with numeric calculation. Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how your language handles numbers that are too large or too small for its underlying representation.

Implementation — Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.

Implementation — Use the appropriate type for the desired action. For example, in C/C++, only use unsigned types for values that could never be negative, such as height, width, or other numbers related to quantity.

Architecture and Design — Use languages, libraries, or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).

Architecture and Design — Use languages, libraries, or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).

References

  • CWE page: https://cwe.mitre.org/data/definitions/682.html
  • CWE list: https://cwe.mitre.org/data/index.html