Adobe Framemaker versions 2029u8 (and earlier) and 2020u4 (and earlier) are affected by an out-of-bounds write vulnerabi
Adobe Framemaker versions 2029u8 (and earlier) and 2020u4 (and earlier) are affected by an out-of-bounds write vulnerabi
Adobe Framemaker versions 2029u8 (and earlier) and 2020u4 (and earlier) are affected by an out-of-bounds write vulnerabi
Adobe Framemaker versions 2029u8 (and earlier) and 2020u4 (and earlier) are affected by an out-of-bounds write vulnerabi
Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.4968.
Inkscape version 0.91 is vulnerable to an out-of-bounds write, which may allow an attacker to arbitrary execute code.
Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.4977.
A vulnerability has been identified in Simcenter Femap (All versions < V2022.2). The affected application contains an ou
WASM3 v0.5.0 was discovered to contain a heap overflow via the component /wabt/bin/poc.wasm.
Delta Electronics DIAScreen versions prior to 1.1.0 are vulnerable to an out-of-bounds write condition, which may result
Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
A crafted NTFS image can cause a heap-based buffer overflow in ntfs_names_full_collate in NTFS-3G through 2021.8.22.
A crafted NTFS image can cause a heap-based buffer overflow in ntfs_mft_rec_alloc in NTFS-3G through 2021.8.22.
A crafted NTFS image can cause a heap-based buffer overflow in ntfs_check_log_client_array in NTFS-3G through 2021.8.22.
A memory corruption issue was addressed with improved memory handling. This issue is fixed in iOS 15.4 and iPadOS 15.4,
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in tvOS 15.5, watchOS 8.6,
A memory corruption issue was addressed with improved validation. This issue is fixed in tvOS 15.5, iOS 15.5 and iPadOS
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in Security Update 2022-00
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in Security Update 2022-00
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in tvOS 15.5, macOS Monter
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in tvOS 15.5, macOS Monter
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in tvOS 15.5, macOS Monter
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in tvOS 15.5, macOS Monter
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in tvOS 15.5, macOS Monter
A memory corruption issue was addressed with improved state management. This issue is fixed in iOS 15.5 and iPadOS 15.5.
A memory corruption issue was addressed with improved input validation. This issue is fixed in iTunes 12.12.4 for Window
An out-of-bounds write issue was addressed with improved input validation. This issue is fixed in Security Update 2022-0
A memory corruption issue was addressed with improved memory handling. This issue is fixed in Security Update 2022-004 C
A memory corruption issue was addressed with improved state management. This issue is fixed in macOS Monterey 12.4, watc
A memory corruption issue was addressed with improved input validation. This issue is fixed in Security Update 2022-004
A memory corruption issue was addressed with improved state management. This issue is fixed in watchOS 8.6, tvOS 15.5, i
A memory corruption issue was addressed with improved state management. This issue is fixed in macOS Monterey 12.4. An a
Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
An issue was discovered in swftools through 20201222. A heap-buffer-overflow exists in the function handleEditText() loc
An issue was discovered in swftools through 20201222. A heap buffer overflow exists in the function swf_FontExtract_Defi
An issue was discovered in swftools through 20201222. A heap-buffer-overflow exists in the function swf_GetD64() located
An issue was discovered in swftools through 20201222. A heap-buffer-overflow exists in the function swf_GetBits() locate
A flaw out of bounds memory write in the Linux kernel UDF file system functionality was found in the way user triggers s
The affected product is vulnerable to an out-of-bounds write, which may allow an attacker to execute arbitrary code.
The affected product is vulnerable to an out-of-bounds write via uninitialized pointer, which may allow an attacker to e
ftbench.c in FreeType Demo Programs through 2.12.1 has a heap-based buffer overflow.
Das U-Boot 2022.01 has a Buffer Overflow, a different issue than CVE-2022-30552.
Out-of-bounds Write in GitHub repository vim/vim prior to 8.2.
Adobe Premiere Pro version 15.4 (and earlier) are affected by a memory corruption vulnerability. An unauthenticated atta
Adobe Media Encoder version 15.4 (and earlier) are affected by a memory corruption vulnerability. An unauthenticated att
Adobe Media Encoder version 15.4 (and earlier) are affected by a memory corruption vulnerability. An unauthenticated att
Heap-based buffer overflow exists in the simulator module contained in the graphic editor 'V-SFT' versions prior to v6.1
Out-of-bounds write vulnerability exists in V-Server v4.0.11.0 and earlier and V-Server Lite v4.0.13.0 and earlier, whic
In nfa_dm_check_set_config of nfa_dm_main.cc, there is a possible out of bounds write due to a missing bounds check. Thi
Frequently Asked Questions
What is CWE-787?
CWE-787 (Out-of-bounds Write) is a weakness category in the Common Weakness Enumeration (CWE) system maintained by MITRE. It describes a class of software or hardware vulnerability that can lead to security issues.
How many CVEs are classified as CWE-787?
There are 17,111 CVE records associated with CWE-787 in our database. Of these, 2513 are critical severity, 8761 are high severity, and 2814 are medium severity.
How can I protect against CWE-787 vulnerabilities?
Protection strategies depend on the specific weakness type. General measures include input validation, secure coding practices, regular security testing, and keeping software up to date. CyberStrike can help by automatically scanning your infrastructure for vulnerabilities related to CWE-787 using AI-powered security agents.
Detect CWE-787 Vulnerabilities
CyberStrike's AI agents automatically detect out-of-bounds write vulnerabilities across your infrastructure.
Get Started