이름: Buffer Over-read

The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.

일반 정보

취약점 도입 방식

Implementation

적용 가능한 플랫폼

언어

클래스: Memory-Unsafe (Undetermined)
이름: C (Undetermined)
이름: C++ (Undetermined)

일반적인 결과

범위	영향	가능성
Confidentiality	Read Memory
Confidentiality	Bypass Protection Mechanism 참고: By reading out-of-bounds memory, an attacker might be able to get secret values, such as memory addresses, which can bypass protection mechanisms such as ASLR in order to improve the reliability and likelihood of exploiting a separate weakness to achieve code execution instead of just denial of service.
Availability Integrity	DoS: Crash, Exit, or Restart 참고: An attacker might be able to cause a crash or other denial of service by causing the product to read a memory location that is not allowed (such as a segmentation fault), or to cause other conditions in which the read operation returns more data than is expected.

관찰된 예시

참고 자료	설명
CVE-2026-7320	Out-of-bounds read in audio processor used in a common web browser, allowing a read of the global data section
CVE-2022-1733	Text editor has out-of-bounds read past end of line while indenting C code
CVE-2014-0160	Chain: "Heartbleed" bug receives an inconsistent length parameter (CWE-130) enabling an out-of-bounds read (CWE-126), returning memory that could include private cryptographic keys and other sensitive data.
CVE-2009-2523	Chain: product does not handle when an input string is not NULL terminated, leading to buffer over-read or heap-based buffer overflow.

탐지 방법

Automated Static Analysis

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.)
효과성 : High

Automated Dynamic Analysis

Use tools that are integrated during compilation to insert runtime error-checking mechanisms related to memory safety errors, such as AddressSanitizer (ASan) for C/C++ [REF-1518].
효과성 : Moderate

취약점 매핑 메모

근거 : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
댓글 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

메모

These problems may be resultant from missing sentinel values (CWE-463) or trusting a user-influenced input length variable.
A buffer over-read typically occurs when the pointer or its index is incremented to a position past the end of the buffer or when pointer arithmetic results in a position after the valid memory location.

참고 자료

REF-1034

Breaking the memory secrecy assumption
Raoul Strackx, Yves Younan, Pieter Philippaerts, Frank Piessens, Sven Lachmund, Thomas Walter.
https://dl.acm.org/doi/10.1145/1519144.1519145

REF-1035

The info leak era on software exploitation
Fermin J. Serna.
https://media.blackhat.com/bh-us-12/Briefings/Serna/BH_US_12_Serna_Leak_Era_Slides.pdf

REF-44

24 Deadly Sins of Software Security
Michael Howard, David LeBlanc, John Viega.

REF-1518

AddressSanitizer
https://clang.llvm.org/docs/AddressSanitizer.html

제출

이름	조직	날짜	출시일	Version
PLOVER		2006-07-19 +00:00	2006-07-19 +00:00	Draft 3

수정 사항

이름	조직	날짜	댓글
CWE Content Team	MITRE	2008-09-08 +00:00	updated Applicable_Platforms, Relationships, Taxonomy_Mappings, Weakness_Ordinalities
CWE Content Team	MITRE	2009-10-29 +00:00	updated Description, Relationship_Notes, Relationships
CWE Content Team	MITRE	2011-03-29 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2012-05-11 +00:00	updated Demonstrative_Examples, Relationships
CWE Content Team	MITRE	2014-06-23 +00:00	updated Observed_Examples
CWE Content Team	MITRE	2014-07-30 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2017-11-08 +00:00	updated Causal_Nature, Demonstrative_Examples
CWE Content Team	MITRE	2018-03-27 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2019-09-19 +00:00	updated Common_Consequences, References
CWE Content Team	MITRE	2020-02-24 +00:00	updated Relationships
CWE Content Team	MITRE	2020-06-25 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2023-01-31 +00:00	updated Description
CWE Content Team	MITRE	2023-04-27 +00:00	updated Detection_Factors, References, Relationships
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2023-10-26 +00:00	updated Observed_Examples
CWE Content Team	MITRE	2025-04-03 +00:00	updated Common_Consequences, Description, Diagram, Other_Notes
CWE Content Team	MITRE	2025-09-09 +00:00	updated Affected_Resources, Common_Consequences, Demonstrative_Examples, Functional_Areas
CWE Content Team	MITRE	2025-12-11 +00:00	updated Applicable_Platforms, Detection_Factors, References
CWE Content Team	MITRE	2026-10-28 +00:00	updated Demonstrative_Examples, Observed_Examples, Relationships

CWE-126 상세 정보

CWE-126