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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

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

1064 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, AvailabilityExecute 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, ConfidentialityRead 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.
ConfidentialityRead 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)
RequirementsUse 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 DesignUse 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 CompilationUse 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
ImplementationConsider 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 CompilationRun 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 IDTitleCVSSSeverityPublished
CVE-2022-34407 Dell PowerEdge Server BIOS 缓冲区错误漏洞 — PowerEdge Platform 7.5 High2023-03-16
CVE-2022-34406 Dell PowerEdge Server BIOS 缓冲区错误漏洞 — PowerEdge Platform 7.5 High2023-03-16
CVE-2023-22881 Denial of Service in Zoom Clients — Zoom (for Android, iOS, Linux, macOS, and Windows) clients before version 5.13.5 6.5 Medium2023-03-16
CVE-2023-22882 Denial of Service in Zoom Clients — Zoom (for Android, iOS, Linux, macOS, and Windows) clients before version 5.13.5 6.5 Medium2023-03-16
CVE-2023-27403 Siemens Tecnomatix Plant Simulation 缓冲区错误漏洞 — Tecnomatix Plant Simulation 7.8 High2023-03-14
CVE-2019-8720 Red Hat Quay 缓冲区错误漏洞 — webkitgtk 8.8 -2023-03-06
CVE-2023-24564 Siemens Solid Edge 缓冲区错误漏洞 — Solid Edge SE2022 7.8 High2023-02-14
CVE-2022-47977 Siemens JT Open Toolkit 缓冲区错误漏洞 — JT Open 7.8 High2023-02-14
CVE-2022-34377 Dell PowerEdge Server BIOS 缓冲区错误漏洞 — PowerEdge Platform 1.9 Low2023-02-10
CVE-2022-34376 Dell PowerEdge Server BIOS 缓冲区错误漏洞 — PowerEdge Platform 3.9 Low2023-02-10
CVE-2023-0251 CVE-2023-0251 — DIAScreen 7.8 High2023-02-08
CVE-2022-43762 Memory leak when receiving messages in APROL Tbase server — B&R APROL 7.5 High2023-02-08
CVE-2023-0637 TRENDnet TEW-811DRU Web Management Interface wan.asp memory corruption — TEW-811DRU 6.5 Medium2023-02-02
CVE-2023-0618 TRENDnet TEW-652BRP Web Service cfg_op.ccp memory corruption — TEW-652BRP 7.5 High2023-02-01
CVE-2023-0613 TRENDnet TEW-811DRU httpd security.asp memory corruption — TEW-811DRU 7.5 High2023-02-01
CVE-2022-32512 Schneider Electric CanBRASS 缓冲区错误漏洞 — CanBRASS 5.3 Medium2023-01-30
CVE-2022-42377 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 7.8 -2023-01-26
CVE-2022-42286 NVIDIA DGX 安全漏洞 — NVIDIA DGX servers 6.0 Medium2023-01-13
CVE-2022-42278 NVIDIA BMC 安全漏洞 — NVIDIA DGX servers 7.2 High2023-01-13
CVE-2022-3161 Siemens Teamcenter Visualization 和 JT2Go 缓冲区错误漏洞 — JT2Go 7.8 High2023-01-13
CVE-2022-3628 Linux kernel 缓冲区错误漏洞 — Kernel 6.6 -2023-01-12
CVE-2023-23457 Upx: segv on packlinuxelf64::invert_pt_dynamic() in p_lx_elf.cpp 5.3 Medium2023-01-12
CVE-2022-38105 ASUS RT-AX82U 缓冲区错误漏洞 — RT-AX82U 7.5 -2023-01-10
CVE-2022-47967 Siemens Solid Edge 缓冲区错误漏洞 — Solid Edge 7.8 High2023-01-10
CVE-2022-47935 Siemens JT Open Toolkit 缓冲区错误漏洞 — JT Open 7.8 High2023-01-10
CVE-2022-3715 Bash 缓冲区错误漏洞 — bash 7.8 -2023-01-05
CVE-2022-4639 sslh Packet Dumping probe.c hexdump format string — sslh 5.6 Medium2022-12-21
CVE-2020-36619 multimon-ng demod_flex.c add_ch format string — multimon-ng 5.5 Medium2022-12-19
CVE-2022-4603 ppp pppdump pppdump.c dumpppp array index — ppp 4.3 Medium2022-12-18
CVE-2022-2947 Altair HyperView Player 缓冲区错误漏洞 — HyperView Player 7.8 High2022-12-13

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