In WLAN driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In WLAN driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In WLAN driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In WLAN driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In WLAN driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In WLAN driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In WLAN driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In audio DSP, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation
When sending malicous data to kernel by ioctl cmd FBIOPUT_VSCREENINFO,kernel will write memory out of bounds.
A stack-based buffer overflow vulnerability [CWE-121] in the command line interpreter of FortiOS before 7.0.4 and FortiP
In camera isp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalatio
In camera isp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalatio
In camera isp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalatio
In mailbox, there is a possible out of bounds write due to type confusion. This could lead to local escalation of privil
In mailbox, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In mailbox, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In mailbox, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
In mailbox, there is a possible out of bounds write due to type confusion. This could lead to local escalation of privil
In wifi driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In wifi driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In wifi driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In wifi driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In wifi driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In wifi driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In wifi driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In wifi driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In v4l2_m2m_querybuf of v4l2-mem2mem.c, there is a possible out of bounds write due to improper input validation. This c
Out of bounds write for some Intel(R) PROSet/Wireless WiFi products may allow a privileged user to potentially enable es
A heap-based buffer overflow was found in the Linux kernel's LightNVM subsystem. The issue results from the lack of prop
In apusys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In apusys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In gz, there is a possible memory corruption due to incorrect error handling. This could lead to local escalation of pri
In vow, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In vow, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In vow, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of
In vow, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of
In audio ipi, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalat
In rpmb, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation o
In aie, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of
In smc_intc_request_fiq of arm_gic.c, there is a possible out of bounds write due to improper input validation. This cou
Memory corruption in kernel due to improper input validation while processing ION commands in Snapdragon Auto, Snapdrago
In wlan, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p
In cpu dvfs, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation
In vowe, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p
drivers/usb/mon/mon_bin.c in usbmon in the Linux kernel before 5.19.15 and 6.x before 6.0.1 allows a user-space client t
The issue was addressed with improved memory handling. This issue is fixed in iOS 16.1 and iPadOS 16, macOS Ventura 13.
In gpu drm, there is a possible out of bounds write due to improper input validation. This could lead to local escalatio
In isp, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of
In isp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In (TBD) of (TBD), there is a possible way to corrupt memory due to improper input validation. This could lead to local
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