目标达成 感谢每一位支持者 — 我们达成了 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-2026-123268 libyal libvmdk 内存破坏漏洞 — libvmdk 3.5 Low 2026-11-05
CVE-2026-122146 fflate 内存破坏漏洞 — fflate 7.3 High 2026-11-05
CVE-2026-121074 Chrome Android 157 之前 GPU 内存损坏漏洞 — Chrome - - 2026-11-03
CVE-2026-121229 Chrome 157 前 Android 版 ANGLE 远程代码执行漏洞 — Chrome - - 2026-11-03
CVE-2026-120232 Horizon DataSys 驱动内存破坏漏洞 — Reboot Restore Standard 8.8 High 2026-11-01
CVE-2026-116259 libimobiledevice afc.c 内存破坏漏洞 — libimobiledevice 5.3 Medium 2026-10-26
CVE-2026-20197 思科Snort 3 Teredo协议拒绝服务漏洞 — Cisco Open Source Snort3 5.8 Medium 2026-10-21
CVE-2026-113003 Chrome 156 之前版本 HID 内存破坏漏洞 — Chrome - - 2026-10-20
CVE-2026-110914 Google Chrome<155.0.8059.84 Workers内存损坏漏洞 — Chrome - - 2026-10-15
CVE-2026-110920 Chrome<155.0.8059.84 V8堆损坏远程代码执行漏洞 — Chrome - - 2026-10-15
CVE-2026-110917 Chrome <155.0.8059.84 SVG内存损坏漏洞 — Chrome - - 2026-10-15
CVE-2026-110918 Chrome<155.0.8059.84内存损坏漏洞 — Chrome - - 2026-10-15
CVE-2026-110913 Google Chrome多个版本DOM内存损坏远程代码执行漏洞 — Chrome - - 2026-10-15
CVE-2026-45450 Unitronics 内存缓冲区越界操作漏洞 — Unitronics UniStream Pro/UniLogic 8.3 High 2026-10-15
CVE-2026-96265 IBM Power Systems 固件内存缓冲区限制不当 — PowerVM Hypervisor 8.2 High 2026-10-12
CVE-2026-84058 IBM Guardium 嗅探器组件多个漏洞 — Guardium Data Protection 8.1 High 2026-10-08
CVE-2026-84875 IBM Guardium Data Protection Sniffer 多个漏洞 — Guardium Data Protection 7.5 High 2026-10-08
CVE-2026-82335 IBM Guardium Data Protection 缓冲区溢出漏洞 — Guardium Data Protection 8.1 High 2026-10-08
CVE-2026-82344 IBM Guardium Data Protection 缓冲区溢出漏洞 — Guardium Data Protection 8.1 High 2026-10-08
CVE-2026-84290 IBM Guardium S-TAP 安全漏洞 — Guardium Data Protection 5.1 Medium 2026-10-08
CVE-2026-106067 Gimp 在 oversized 图像的热色滤镜中堆缓冲区溢出漏洞 — Red Hat Enterprise Linux 10 6.3 Medium 2026-10-07
CVE-2026-106066 GIMP 堆缓冲区溢出漏洞:处理超大图像尺寸时 — Red Hat Enterprise Linux 10 6.3 Medium 2026-10-07
CVE-2026-106065 GIMP oversized image dimensions 堆缓冲区溢出漏洞 — Red Hat Enterprise Linux 10 6.3 Medium 2026-10-07
CVE-2026-76464 Cisco Meraki 10/2026 加固版本缓冲区管理漏洞 — Cisco Campus Gateway Software 9.6 Critical 2026-10-07
CVE-2026-106064 GIMP GIF导出堆缓冲区溢出漏洞 — Red Hat Enterprise Linux 10 6.3 Medium 2026-10-07
CVE-2026-106062 GIMP DDS加载器堆缓冲区溢出漏洞 — Red Hat Enterprise Linux 9 7.8 High 2026-10-06
CVE-2026-106063 GIMP DICOM导出堆缓冲区溢出漏洞 — Red Hat Enterprise Linux 10 6.3 Medium 2026-10-06
CVE-2026-47602 NVIDIA驱动解引用漏洞致拒绝服务与信息泄露 — GeForce 7.1 High 2026-09-30
CVE-2026-47550 NVIDIA Windows驱动内核空指针解引用漏洞 — GeForce 7.8 High 2026-09-30
CVE-2026-100892 UERANSIM nr-gnb handler.cpp UL信息传输内存损坏漏洞 — UERANSIM 5.3 Medium 2026-09-28

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