In da, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pri
A stack-based buffer overflow vulnerability (CWE-121) in the profile parser of FortiSandbox version 3.2.2 and below, ver
In DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pri
In DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pri
In wbrc_bt_dev_write of wb_regon_coordinator.c, there is a possible out of bounds write due to a buffer overflow. This c
In m4u, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In power, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In Modem, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation
Memory corruption when input parameter validation for number of fences is missing for fence frame IOCTL calls,
In BnDmAgent::onTransact of dm_agent.cpp, there is a possible out of bounds write due to a missing bounds check. This co
In secmem, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
A flaw was found in grub2. A specially crafted JPEG file can cause the JPEG parser of grub2 to incorrectly check the bou
When reading the language .mo file in grub_mofile_open(), grub2 fails to verify an integer overflow when allocating its
A flaw was found in grub2. When reading a symbolic link's name from a UFS filesystem, grub2 fails to validate the string
A flaw was found in grub2. The calculation of the translation buffer when reading a language .mo file in grub_gettext_ge
A flaw was found in grub2. When reading tar files, grub2 allocates an internal buffer for the file name. However, it fai
In vdec, there is a possible permission bypass due to improper input validation. This could lead to local escalation of
Out-Of-Bounds Write in TPM2 Reference Library in Google ChromeOS 15753.50.0 stable on Cr50 Boards allows an attacker wi
Out-Of-Bounds Write in TPM2 Reference Library in Google ChromeOS 122.0.6261.132 stable on Cr50 Boards allows an attacke
Out-of-bounds write in Keymaster trustlet prior to SMR May-2025 Release 1 allows local privileged attackers to write out
A vulnerability has been identified in SCALANCE LPE9403 (6GK5998-3GS00-2AC2) (All versions < V4.0 HF0). Affected devices
A vulnerability has been identified in SCALANCE LPE9403 (6GK5998-3GS00-2AC2) (All versions < V4.0 HF0). Affected devices
A flaw was found in polkit. When processing an XML policy with 32 or more nested elements in depth, an out-of-bounds wri
In Power HAL, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation
In Power HAL, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation
In lwis_top_register_io of lwis_device_top.c, there is a possible out of bounds write due to an incorrect bounds check.
NVIDIA Bluefield and ConnectX contain a vulnerability in the management interface that could allow a malicious actor wit
In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local es
In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local es
In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local es
In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local es
In gnss service, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local esca
In gnss service, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local esca
In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local es
In charger, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
NVIDIA DGX Spark GB10 contains a vulnerability in SROOT firmware where an attacker could cause an out-of-bound write. A
In display, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In display, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In display, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In V6 DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In V6 DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In V6 DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In V5 DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In V5 DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In V6 DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pri
In DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pri
In DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pri
Memory corruption while processing frame packets.
Memory corruption while accessing MSM channel map and mixer functions.
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