Cyber Resilience

CWE · MITRE source

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

Abstraction: Base · CVEs in our corpus: 103

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: 21 August 2026 07:11 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: partial · 2 mapping(s) from 2 framework(s): CAPEC 1 (partial) · STIG windows 10 1 (partial)

See the full cumulative-coverage rollup →

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • PR.PS-06
  • ID.RA-01
  • SA-8 Security and Privacy Engineering Principles
  • SA-11 Developer Testing and Evaluation
Detect
Catch it (CSF Detect / Respond)

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.4.1

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

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

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2023-33106 KEV 8.98.40.00852023-12-05
CVE-2023-24855 7.39.80.00542023-10-03
CVE-2023-22388 7.29.80.00352023-11-07
CVE-2023-43553 7.29.80.00352024-03-04
CVE-2017-11076 7.29.80.00342024-11-26
CVE-2016-2161 7.17.50.20952017-07-27
CVE-2020-6112 7.07.80.17092020-09-17
CVE-2020-27009 6.98.10.07192021-04-22
CVE-2022-0729 6.98.80.01622022-02-23
CVE-2023-46724 6.88.60.04052023-11-01
CVE-2026-46244 6.89.10.00322026-06-03
CVE-2026-21732 6.69.60.00292026-03-20
CVE-2026-726426.58.80.00332026-08-13
CVE-2020-13573 6.47.50.03422021-01-07
CVE-2021-3888 6.48.10.01292021-10-19
CVE-2021-3889 6.48.10.01292021-10-19
CVE-2023-43534 6.48.60.00262024-02-06
CVE-2021-34595 6.38.10.00882021-10-26
CVE-2022-32142 6.38.10.01022022-06-24
CVE-2023-20187 6.38.60.00652023-09-27
CVE-2022-0554 6.27.80.01612022-02-10
CVE-2022-0685 6.27.80.01722022-02-20
CVE-2024-42416 6.28.80.00402024-09-05
CVE-2024-423866.28.20.00352024-11-18
CVE-2026-12290 6.18.10.00402026-06-16