CWE-190: Integer Overflow or Wraparound¶
MITRE Corporation. (2026). CWE-190: Integer Overflow or Wraparound.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Integer Overflow
- … bytes_per_pixel` in an image decoder, or `n_items * sizeof(item)` in an allocator — that overflows to a small value, causing an undersized buffer to be allocated; the subsequent write of the full intended data overruns the buffer, producing a heap or stack overflow that an attacker exploits for remote code execution.
This sourceThe catalogue entry whose description, allocator examples and consequence list give exactly this chain - an overflowing size calculation, an undersized allocation, a subsequent buffer overflow and arbitrary code execution - and which records CWE-680 as its child for the overflow-to-overrun step.
SupportedVerified against the source
- … bytes_per_pixel` in an image decoder, or `n_items * sizeof(item)` in an allocator — that overflows to a small value, causing an undersized buffer to be allocated; the subsequent write of the full intended data overruns the buffer, producing a heap or stack overflow that an attacker exploits for remote code execution.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:a26ac5001006 · see in the full table