Cyber Resilience

CWE · MITRE source

CWE-823Use of Out-of-range Pointer Offset

Abstraction: Base · CVEs in our corpus: 98

The product performs pointer arithmetic on a valid pointer, but it uses an offset that can point outside of the intended range of valid memory locations for the resulting pointer.

While a pointer can contain a reference to any arbitrary memory location, a program typically only intends to use the pointer to access limited portions of memory, such as contiguous memory used to access an individual array. Programs may use offsets in order to access fields or sub-elements stored within structured data. The offset might be out-of-range if it comes from an untrusted source, is the result of an incorrect calculation, or occurs because of another error. If an attacker can control or influence the offset so that it points outside of the intended boundaries of the structure, then the attacker may be able to read or write to memory locations that are used elsewhere in the product. As a result, the attack might change the state of the product as accessed through program variables, cause a crash or instable behavior, and possibly lead to code execution.

Last updated: 04 July 2026 00:28 UTC

Cumulative inbound coverage

How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.

Collective: mostly · 8 mapping(s) from 4 framework(s): ATT&CK 5 (partial) · ASVS 5.0 1 (mostly) · CAPEC 1 (partial) · STIG windows 10 1 (partial)

See the full cumulative-coverage rollup →

NIST 800-53 r5 controls that address this weakness (0)AI

Control Title Family Why it addresses this CWE
No NIST controls proposed yet.

MITRE ATT&CK techniques this weakness enables

Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.

Direction: other covers this; this covers other (F/M/P = full / mostly / partial).

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2023-33106 KEV10.08.40.00852023-12-05
CVE-2023-248557.09.80.00542023-10-03
CVE-2023-223887.09.80.00352023-11-07
CVE-2023-435537.09.80.00352024-03-04
CVE-2017-110767.09.80.00342024-11-26
CVE-2026-217327.09.60.00292026-03-20
CVE-2026-46244 UPD7.09.10.00312026-06-03
CVE-2016-21616.07.50.20952017-07-27
CVE-2020-61126.07.80.17092020-09-17
CVE-2020-135735.57.50.03392021-01-07
CVE-2021-13525.57.40.00402021-03-24
CVE-2020-270095.58.10.07192021-04-22
CVE-2021-38885.58.10.01202021-10-19
CVE-2021-38895.58.10.01202021-10-19
CVE-2021-345955.58.10.00852021-10-26
CVE-2022-05545.57.80.01612022-02-10
CVE-2022-06855.57.80.01722022-02-20
CVE-2022-07295.58.80.01622022-02-23
CVE-2022-321425.58.10.00982022-06-24
CVE-2022-422645.57.10.00282022-12-30
CVE-2022-256945.58.40.00122023-03-10
CVE-2022-257095.58.40.00122023-03-10
CVE-2023-223875.57.80.00112023-07-04
CVE-2023-285645.57.80.00112023-09-05
CVE-2023-201875.58.60.00652023-09-27