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-2023-36861 GTKWave 缓冲区错误漏洞 — GTKWave 7.8 High2024-01-08
CVE-2023-38648 GTKWave 安全漏洞 — GTKWave 7.8 High2024-01-08
CVE-2023-38649 GTKWave 安全漏洞 — GTKWave 7.8 High2024-01-08
CVE-2023-34436 GTKWave 缓冲区错误漏洞 — GTKWave 7.8 High2024-01-08
CVE-2023-38657 GTKWave 缓冲区错误漏洞 — GTKWave 7.8 High2024-01-08
CVE-2023-39443 GTKWave 缓冲区错误漏洞 — GTKWave 7.8 High2024-01-08
CVE-2023-39444 GTKWave 缓冲区错误漏洞 — GTKWave 7.8 High2024-01-08
CVE-2023-41779 Illegal Memory Access Vulnerability of ZTE's ZXCLOUD iRAI — ZXCLOUD iRAI 4.4 Medium2024-01-03
CVE-2023-28587 Improper Restriction of Operations within the Bounds of a Memory Buffer in BT Controller — Snapdragon 7.8 High2023-12-05
CVE-2023-28586 Improper Restriction of Operation within the Bounds of a Memory Buffer in TZ Secure OS — Snapdragon 6.0 Medium2023-12-05
CVE-2023-28551 Improper Restriction of Operations within the Bounds of a Memory Buffer in UTILS — Snapdragon 7.8 High2023-12-05
CVE-2023-28550 Improper Restriction of Operations within the Bounds of a Memory Buffer in MPP Performance — Snapdragon 7.8 High2023-12-05
CVE-2023-21634 Improper Restriction of Operations within the Bounds of a Memory Buffer in Radio Interface Layer — Snapdragon 6.7 Medium2023-12-05
CVE-2023-45168 IBM AIX command execution — AIX 8.4 High2023-12-01
CVE-2023-49701 Out-of-bounds access a buffer in SIM management — Falcon 7.2 High2023-11-30
CVE-2023-49699 Out-of-bounds access a buffer in IMS — Falcon 6.7 Medium2023-11-30
CVE-2021-38405 Siemens Solid Edge, JT2Go, and Teamcenter Visualization Improper Restriction of Operations within the Bounds of a Memory Buffer — JT2Go 7.8 High2023-11-21
CVE-2023-24585 Micrium uC-HTTP 缓冲区错误漏洞 — Gecko Platform 7.7 High2023-11-14
CVE-2023-28391 Weston Embedded uC-HTTP 缓冲区错误漏洞 — Gecko Platform 9.0 Critical2023-11-14
CVE-2023-28379 Micrium uC-HTTP 缓冲区错误漏洞 — Gecko Platform 9.0 Critical2023-11-14
CVE-2023-31247 Micrium uC-HTTP 缓冲区错误漏洞 — Gecko Platform 9.0 Critical2023-11-14
CVE-2023-4949 Memory Corruption Vulnerability in Grub-Legacy's XFS Implementation — Grub-Legacy 8.1 High2023-11-10
CVE-2023-3889 Mali GPU Kernel Driver exposes sensitive data from freed memory — Valhall GPU Kernel Driver 7.8 -2023-11-07
CVE-2023-28545 Improper Restriction of Operations within the Bounds of a Memory Buffer in TZ Secure OS — Snapdragon 8.2 High2023-11-07
CVE-2023-40661 Opensc: multiple memory issues with pkcs15-init (enrollment tool) 5.4 Medium2023-11-06
CVE-2022-4900 Potential buffer overflow in php_cli_server_startup_workers — php 6.2 Medium2023-11-02
CVE-2023-4967 Denial of service — NetScaler ADC 8.2 High2023-10-27
CVE-2023-44184 Junos OS and Junos OS Evolved: High CPU load due to specific NETCONF command — Junos OS 6.5 Medium2023-10-12
CVE-2023-4966 Unauthenticated sensitive information disclosure — NetScaler ADC 9.4 Critical2023-10-10
CVE-2023-3576 Libtiff: memory leak in tiffcrop.c — Red Hat Enterprise Linux 9 5.5 Medium2023-10-04

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