目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1359 元

100%

CWE-119 内存缓冲区边界内操作的限制不恰当 类漏洞列表 1131

CWE-119 内存缓冲区边界内操作的限制不恰当 类弱点 1131 条 CVE 漏洞汇总,含 AI 中文分析。

CWE-119 属于内存缓冲区操作限制不当漏洞,指程序在读写内存时超出缓冲区边界,导致意外访问其他变量或内部数据。攻击者通常利用此缺陷通过精心构造的输入触发缓冲区溢出,从而覆盖关键内存数据或执行任意代码,实现远程代码执行或系统崩溃。开发者应避免此类风险,需严格实施边界检查,使用安全的字符串处理函数,并启用编译器防护机制,确保所有内存操作均在合法范围内进行。

MITRE CWE 官方描述
CWE:CWE-119 内存缓冲区操作限制不当 (Improper Restriction of Operations within the Bounds of a Memory Buffer) 英文:产品对内存缓冲区执行操作,但其从内存缓冲区的预期边界之外读取或写入内存位置。这可能导致对意外内存位置的读取或写入操作,这些位置可能与其它变量、数据结构或内部程序数据相关联。
常见影响 (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.
缓解措施 (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
代码示例 (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 标题 CVSS 风险等级 Published
CVE-2025-53715 TP-LINK TL-WR841N 安全漏洞 — TL-WR841N V11 7.5AI High AI 2025-07-29
CVE-2025-53714 TP-LINK TL-WR841N 安全漏洞 — TL-WR841N V11 7.5AI High AI 2025-07-29
CVE-2025-33077 IBM Engineering Systems Design Rhapsody 缓冲区错误漏洞 — Engineering Systems Design Rhapsody 8.8 High 2025-07-23
CVE-2025-33076 IBM Engineering Systems Design Rhapsody 缓冲区错误漏洞 — Engineering Systems Design Rhapsody 8.8 High 2025-07-23
CVE-2025-7299 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7325 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7323 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7321 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7320 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7318 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7317 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7316 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7315 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7314 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7313 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7311 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7309 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7310 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7308 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7307 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7306 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7305 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7304 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7303 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7302 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7301 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7300 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7296 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7297 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21
CVE-2025-7295 IrfanView CADImage Plugin 缓冲区错误漏洞 — IrfanView 7.8 - 2025-07-21

CWE-119(内存缓冲区边界内操作的限制不恰当) 是常见的弱点类别,本平台收录该类弱点关联的 1131 条 CVE 漏洞。