Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-119
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.
We track 2,498 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 8.6. 59 have been exploited in real attacks.
How this weakness is prevented
- Requirements: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Operation Build and Compilation: Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
- Operation: Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment. For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND.
- Implementation: Replace unbounded copy functions with analogous functions that support length arguments, such as strcpy with strncpy. Create these if they are not available.
Latest Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities
- 9.9 Critical severity
BR6478ACV2: Improper Restriction of Operations within the Bounds of a Memory Buffer
A security vulnerability has been detected in Edimax BR6478ACV2 1.23. The impacted element is the function formPPTPSetup of the file webs. The manipulation of the argument pptpUserName leads to buffer overflow. It is possible to initiate the attack remotely. T
- 7.8 High severity
Origin Viewer: Improper Restriction of Operations within the Bounds of a Memory Buffer
OriginLab Origin Viewer OGM File Parsing Memory Corruption Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of OriginLab Origin Viewer. User interaction is required to exploit t
- 8.8 High severity
Chrome: Improper Restriction of Operations within the Bounds of a Memory Buffer
Memory corruption in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
- 8.4 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In acquireMemory of bt_bqr_offload.cc, there is a possible way to trigger an out of bounds write via a buffer size underflow due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User
- 8.4 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In multiple locations, there is a possible way to trigger an out of bounds write in the shared memory tracking bitmap due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interacti
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In slice_header of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In knee_function_info of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 8.4 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In StNfc_hal_write of hal_st21nfc.cc, there is a possible way to trigger an out of bounds write into global memory due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interacti
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In sub_layer_hrd_parameters of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In cpb_cnt of avc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In s_inter_rps_pred of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 7.5 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In CompareTelUris of SipAddress.cpp, there is a possible way to trigger an unhandled out of range exception and process crash due to an incorrect bounds check. This could lead to remote denial of service with no additional execution privileges needed. User int
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In prev_run_vcore of hwcodec_firmware, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In buffering_period of avc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In tone_mapping_info of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In s_av1_dec_metadata_scalability of av1_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploit
- 8.4 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In stpropnci_prop_st_build_set_custom_polling_cmd of stpropnci_prop_st.cc, there is a possible way to trigger an out of bounds write into global memory due to a missing bounds check. This could lead to local escalation of privilege with no additional execution
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In s_check_valid_tile_param_custom_tile of av1_encoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In max_num_ref_frames of avc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 8.4 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In ExecuteGraphCommand of multiple files, there is a possible way to trigger an out of bounds write via an oversized scratch memory declaration due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution priv
- 9.8 Critical severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In multiple functions of rmmi_utility.c, there is a possible way to trigger an out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploi
- 8.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In multiple functions of cn_Tai.cpp, there is a possible way to trigger an out of bounds write due to memory corruption. This could lead to remote (proximal/adjacent) code execution with no additional execution privileges needed. User interaction is not needed
- 8.4 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In multiple functions of AndroidManifest.xml, there is a possible way to trigger unauthorized firmware updates via exported broadcast receivers due to a missing permission check. This could lead to local escalation of privilege with no additional execution pri
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In pic_timing of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In CMD_ENC_SET_PARAM of encoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 8.4 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In stpropnci_process_std of stpropnci_std.cc, there is a possible way to trigger an out of bounds write into global state due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User inter
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In cnm_memset of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 9.8 Critical severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In multiple locations, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In mfc_alloc_enc_roi_buffer of mfc_buf.c, there is a possible out-of-bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
- 9.8 Critical severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In handleEvent of gscan.cpp, there is a possible way to trigger an out of bounds write on the heap due to a missing bounds check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed f
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In codec3p_secure of codec3p_secure, there is a possible Heap Buffer Overflow due to a missing bounds check. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 9.8 Critical severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In __mfc_core_nal_q_get_dec_metadata_sei_nal of mfc_core_nal_q.c, there is a possible out-of-bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for
- 8.4 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In PresenceDecoderV1::DecodeDataElements of presence_decoder_v1.cc, there is a possible out-of-bounds write due to a missing bounds check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In RecordApTx of efw_ap_transport.c, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 8.4 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In multiple locations, there is a possible way to trigger an out of bounds read and write in shared memory due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is no
- 9.8 Critical severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In multiple files, there is a possible out-of-bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In TzSharedMemory of TzSharedMemory.c, there is a possible Heap buffer overflow due to a logic error in the code. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In parse_prime256v1 of keymint_asn1.c, there is a possible Heap Buffer Overflow due to a logic error in the code. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.
- 8.4 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In thread_free of thread.c, there is a possible way to corrupt kernel heap metadata on thread creation failure due to memory corruption. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not ne
- 7.8 High severity
Android: Improper Restriction of Operations within the Bounds of a Memory Buffer
In insert_node of remap.c, there is a possible way to trigger an out of bounds write in the address remapping table due to a non-heap buffer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is