In the Citadel chip firmware, there is a possible out of bounds write due to a missing bounds check. This could lead to
In the FingerTipS touch screen driver, there is a possible out of bounds write due to a heap buffer overflow. This could
In iaxxx_core_sensor_change_state of iaxxx-module.c, there is a possible out of bounds write due to a missing bounds che
In pb_write of pb_encode.c, there is a possible out of bounds write due to a missing bounds check. This could lead to lo
IBM Informix Dynamic Server 14.10 is vulnerable to a stack based buffer overflow, caused by improper bounds checking. A
An out-of-bounds (OOB) memory write flaw was found in list_devices in drivers/md/dm-ioctl.c in the Multi-device driver m
A stack-based buffer overflow vulnerability in FortiProxy physical appliance CLI 2.0.0 to 2.0.1, 1.2.0 to 1.2.9, 1.1.0 t
An improper input validation vulnerability in NPU firmware prior to SMR MAY-2021 Release 1 allows arbitrary memory write
A heap overflow in LzmaUefiDecompressGetInfo function in EDK II.
In halWrapperDataCallback of hal_wrapper.cc, there is a possible out of bounds write due to a missing bounds check. This
In phNxpNciHal_process_ext_rsp of phNxpNciHal_ext.cc, there is a possible out of bounds write due to an integer overflow
In phNxpNciHal_print_res_status of phNxpNciHal.cc, there is a possible out of bounds write due to a missing bounds check
In phNxpNciHal_print_res_status of phNxpNciHal.cc, there is a possible out of bounds write due to a missing bounds check
In phNxpNciHal_print_res_status of phNxpNciHal.cc, there is a possible out of bounds write due to a missing bounds check
In beginWrite and beginRead of MessageQueueBase.h, there is a possible out of bounds write due to improper input validat
In clk driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escala
In ged, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In OMA DRM, there is a possible memory corruption due to improper input validation. This could lead to local escalation
The firewire subsystem in the Linux kernel through 5.14.13 has a buffer overflow related to drivers/media/firewire/fired
dp_link_settings_write in drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c in the Linux kernel through 5.14.14
Internet Download Manager 6.37.11.1 was discovered to contain a stack buffer overflow in the Search function. This vulne
In display driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local es
In audio DSP, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalat
In audio DSP, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalat
In audio DSP, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalat
In ip6_xmit of ip6_output.c, there is a possible out of bounds write due to a use after free. This could lead to local e
In TBD of TBD, there is a possible out of bounds write due to improper locking. This could lead to local escalation of p
Possible memory corruption due to improper validation of memory address while processing user-space IOCTL for clearing F
In the Linux kernel through 5.15.2, hw_atl_utils_fw_rpc_wait in drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_uti
Out-of-bounds write in the firmware for Intel(R) Ethernet 700 Series Controllers before version 8.2 may allow a privileg
In mdlactl driver, there is a possible memory corruption due to an incorrect bounds check. This could lead to local esca
In apusys, there is a possible out of bounds write due to a stack-based buffer overflow. This could lead to local escala
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 memory corruption due to a missing bounds check. This could lead to local escalation of p
A buffer overflow [CWE-121] in the TFTP client library of FortiOS before 6.4.7 and FortiOS 7.0.0 through 7.0.2, may allo
In phNxpNHal_DtaUpdate of phNxpNciHal_dta.cc, there is a possible out of bounds write due to an incorrect bounds check.
In (TBD) of (TBD), there is a possible out of bounds write due to a missing bounds check. This could lead to local escal
In sec_ts_parsing_cmds of (TBD), there is a possible out of bounds write due to an incorrect bounds check. This could le
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 memory corruption due to a missing bounds check. This could lead to local escalation of p
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 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 apusys, 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 upx canPack in p_lx_elf.cpp in UPX 3.96. This flaw allows attackers to cause a denial of service (SE
track_header in libavformat/vividas.c in FFmpeg 4.3.1 has an out-of-bounds write because of incorrect extradata packing.
Insufficient data validation in V8 in Google Chrome prior to 87.0.4280.88 allowed a remote attacker to potentially explo
In ElementaryStreamQueue::dequeueAccessUnitH264() of ESQueue.cpp, there is a possible out of bounds write due to a missi
In WAVSource::read of WAVExtractor.cpp, there is a possible out of bounds write due to an integer overflow. This could l
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