Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-119 (内存缓冲区边界内操作的限制不恰当) — Vulnerability Class 1131

1131 vulnerabilities classified as CWE-119 (内存缓冲区边界内操作的限制不恰当). AI Chinese analysis included.

CWE-119 represents a critical memory safety weakness where software performs read or write operations beyond the intended boundaries of a memory buffer. This flaw typically arises from insufficient validation of input lengths or loop counters, allowing attackers to manipulate program execution flow. By crafting malicious inputs that exceed buffer limits, adversaries can overwrite adjacent memory, corrupt data structures, or inject executable code, often leading to remote code execution or system crashes. Developers mitigate this risk by implementing rigorous bounds checking before any memory access, utilizing safe string handling functions that enforce length limits, and adopting modern programming languages with automatic memory management. Additionally, employing static analysis tools and fuzzing techniques during development helps identify out-of-bounds accesses early, ensuring that all buffer operations remain strictly within allocated memory regions to prevent exploitation.

MITRE CWE Description
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Common Consequences (3)
Integrity, Confidentiality, Availability Execute Unauthorized Code or Commands, Modify Memory
If the memory accessible by the attacker can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow. If the attacker can overwrite a pointer's worth of memory (usually 32 or 64 bits), they can alter the intended control flow by redirecting a funct…
Availability, Confidentiality Read Memory, DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory)
Out of bounds memory access will very likely result in the corruption of relevant memory, and perhaps instructions, possibly leading to a crash. Other attacks leading to lack of availability are possible, including putting the program into an infinite loop.
Confidentiality Read Memory
In the case of an out-of-bounds read, the attacker may have access to sensitive information. If the sensitive information contains system details, such as the current buffer's position in memory, this knowledge can be used to craft further attacks, possibly with more severe consequences.
Mitigations (5)
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 lan…
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 [REF-57], and the Strsafe.h library from Microsoft [REF-56]. 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 [REF-1334] discusses…
Effectiveness: Defense in Depth
Implementation Consider adhering to the following rules when allocating and managing an application's memory: Double check that the buffer is as large as specified. When using functions that accept a number of bytes to copy, such as strncpy(), be aware that if the destination buffer size is equal to the source buffer size, it may not NULL-terminate the string. Check buffer boundaries if accessing the buffer in a…
Operation, Build and Compilation Run or compile the software using features or extensions that randomly arrange the positions of a program's executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code. Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported…
Effectiveness: Defense in Depth
Examples (2)
This example takes an IP address from a user, verifies that it is well formed and then looks up the hostname and copies it into a buffer.
void host_lookup(char *user_supplied_addr){ struct hostent *hp; in_addr_t *addr; char hostname[64]; in_addr_t inet_addr(const char *cp); /*routine that ensures user_supplied_addr is in the right format for conversion */ validate_addr_form(user_supplied_addr); addr = inet_addr(user_supplied_addr); hp = gethostbyaddr( addr, sizeof(struct in_addr), AF_INET); strcpy(hostname, hp->h_name); }
Bad · C
This example applies an encoding procedure to an input string and stores it into a buffer.
char * copy_input(char *user_supplied_string){ int i, dst_index; char *dst_buf = (char*)malloc(4*sizeof(char) * MAX_SIZE); if ( MAX_SIZE <= strlen(user_supplied_string) ){ die("user string too long, die evil hacker!"); } dst_index = 0; for ( i = 0; i < strlen(user_supplied_string); i++ ){ if( '&' == user_supplied_string[i] ){ dst_buf[dst_index++] = '&'; dst_buf[dst_index++] = 'a'; dst_buf[dst_index++] = 'm'; dst_buf[dst_index++] = 'p'; dst_buf[dst_index++] = ';'; } else if ('<' == user_supplied_string[i] ){ /* encode to &lt; */ } else dst_buf[dst_index++] = user_supplied_string[i]; } return ds
Bad · C
CVE ID Title CVSS Severity Published
CVE-2026-58005 Unvalidated SiP v2 mailbox pointers allow non-secure EL1 access to arbitrary physical addresses through EL3. — Trusted Firmware 8.1 High 2026-09-24
CVE-2026-20352 Cisco Identity Services Engine RADIUS Denial of Service Vulnerability — Cisco Identity Services Engine Software 8.6 High 2026-09-16
CVE-2026-92178 pdfforge PDF Architect PDF File Parsing Memory Corruption Remote Code Execution Vulnerability — PDF Architect - - 2026-09-15
CVE-2026-19886 OriginLab Origin Viewer OGM File Parsing Memory Corruption Remote Code Execution Vulnerability — Origin Viewer - - 2026-09-15
CVE-2026-91091 GPAC Node Insertion base_scenegraph.c gf_node_list_insert_child memory corruption — GPAC 4.3 Medium 2026-09-15
CVE-2026-90831 GNU Binutils ELF String Table elf-strtab.c _bfd_elf_strtab_delref memory corruption — Binutils 5.3 Medium 2026-09-14
CVE-2026-54559 PocketSphinx: Buffer overflows in language and acoustic model loading code — pocketsphinx 6.9 Medium 2026-09-14
CVE-2026-90714 marcobambini Gravity JSON parser gravity_json.c memory corruption — Gravity 6.3 Medium 2026-09-14
CVE-2026-90686 GPAC MP4Box loader_bt.c gf_bt_report memory corruption — GPAC 5.3 Medium 2026-09-14
CVE-2026-90572 davenardella snap7 s7_micro_client.cpp opUpload memory corruption — snap7 4.7 Medium 2026-09-13
CVE-2026-87489 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-09-09
CVE-2026-87444 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-09-09
CVE-2026-9637 CompactLogix® 5380 / ControlLogix® 5580 - Multiple Vulnerabilities — CompactLogix® 5380 / ControlLogix® 5580 8.7 High 2026-09-01
CVE-2026-82596 LatencyUtils PauseDetector LatencyStats.java LatencyStats.recordDetectedPause memory corruption — LatencyUtils 3.3 Low 2026-08-31
CVE-2026-82587 Open5GS AMF namf-handler.c amf_namf_comm_decode_ue_mm_context_list memory corruption — Open5GS 4.3 Medium 2026-08-30
CVE-2026-82539 TOTOLINK A720R MAC Filtering cstecgi.cgi setMacFilterRules memory corruption — A720R 9.1 Critical 2026-08-30
CVE-2026-81581 User input in WibuKey is used (without proper sanitization) to compute the address of a pointer, which can be exploited to let the user point to any storage, to which Windows responds with a denial of service. — wibukey 8.8 High 2026-08-27
CVE-2026-79069 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-08-25
CVE-2026-55586 SumatraPDF: Heap out-of-bounds write in vendored CHMLib LZX Huffman table construction reachable from crafted CHM files — sumatrapdf 6.6 Medium 2026-08-20
CVE-2026-18294 OriginLab Origin Viewer OGW File Parsing Memory Corruption Remote Code Execution Vulnerability — Origin Viewer - - 2026-08-20
CVE-2026-18292 OriginLab OriginPro OGG File Parsing Memory Corruption Remote Code Execution Vulnerability — OriginPro - - 2026-08-20
CVE-2026-18291 OriginLab OriginPro OGW File Parsing Memory Corruption Remote Code Execution Vulnerability — OriginPro - - 2026-08-20
CVE-2026-76987 liftoff-sr CIPster Generic Attribute Logic ciptypes.h SetAttrData memory corruption — CIPster 7.3 High 2026-08-20
CVE-2026-20319 Cisco Secure Workload Software Security Hardening Release August 2026 - Buffer Management Vulnerabilities — Cisco Secure Workload 7.5 High 2026-08-19
CVE-2025-15685 Open5GS freeDiameter memory corruption — Open5GS 6.3 Medium 2026-08-12
CVE-2026-20268 Cisco IOS XE Software Security Hardening Release — Cisco IOS XE Software 8.6 High 2026-08-05
CVE-2026-20156 Cisco RoomOS Security Hardening Release - Buffer Management Vulnerabilities — Cisco RoomOS Software 8.1 High 2026-07-15
CVE-2026-14607 RT-Thread lwp_syscall.c sys_getaddrinfo memory corruption — RT-Thread 5.5 Medium 2026-07-03
CVE-2026-12216 svaarala duktape duk_api_bytecode.c memory corruption — duktape 5.3 Medium 2026-06-15
CVE-2026-0409 Netgear Orbi 370 Series Remote Code Execution vulnerability — Orbi 370 - - 2026-06-09

Vulnerabilities classified as CWE-119 (内存缓冲区边界内操作的限制不恰当) represent 1131 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.