In face detect driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local d
In gpu driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a segmentation violation via the function gf_isom_meta_r
GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a segmentation violation via the function gf_isom_get_me
GPAC 2.1-DEV-rev368-gfd054169b-master was discovered to contain a segmentation violation via the function gf_dump_vrml_s
LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in libtiff/tif_unix.c:346 when called from extractImageSection,
LibTIFF 4.4.0 has an out-of-bounds write in extractContigSamplesShifted24bits in tools/tiffcrop.c:3604, allowing attacke
LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemset in libtiff/tif_unix.c:340 when called from processCropSelections
LibTIFF 4.4.0 has an out-of-bounds write in _TIFFmemcpy in libtiff/tif_unix.c:346 when called from extractImageSection,
rtf2html v0.2.0 was discovered to contain a heap overflow in the component /rtf2html/./rtf_tools.h.
tsMuxer v2.6.16 was discovered to contain a heap overflow via the function BitStreamWriter::flushBits() at /tsMuxer/bitS
pycdc commit 44a730f3a889503014fec94ae6e62d8401cb75e5 was discovered to contain a stack overflow via the component __san
A memory corruption issue was addressed with improved state management. This issue is fixed in iOS 16, macOS Ventura 13.
PicoC Version 3.2.2 was discovered to contain a heap buffer overflow in the ExpressionCoerceInteger function in expressi
PicoC Version 3.2.2 was discovered to contain a heap buffer overflow in the ExpressionCoerceUnsignedInteger function in
PicoC Version 3.2.2 was discovered to contain a heap buffer overflow in the StringStrncpy function in cstdlib/string.c w
PicoC Version 3.2.2 was discovered to contain a heap buffer overflow in the ExpressionAssign function in expression.c wh
PicoC Version 3.2.2 was discovered to contain a heap buffer overflow in the LexGetStringConstant function in lex.c when
PicoC Version 3.2.2 was discovered to contain a heap buffer overflow in the StdioOutPutc function in cstdlib/stdio.c whe
PicoC Version 3.2.2 was discovered to contain a heap buffer overflow in the StringStrcat function in cstdlib/string.c wh
PicoC Version 3.2.2 was discovered to contain a heap buffer overflow in the StdioBasePrintf function in cstdlib/string.c
PicoC Version 3.2.2 was discovered to contain a heap buffer overflow in the ExpressionCoerceFP function in expression.c
PicoC Version 3.2.2 was discovered to contain a heap buffer overflow in the LexSkipComment function in lex.c when called
XPDF v4.04 was discovered to contain a stack overflow via the function FileStream::copy() at xpdf/Stream.cc:795.
A stack overflow in the Catalog::readPageLabelTree2(Object*) function of XPDF v4.04 allows attackers to cause a Denial o
In sensor driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In face detect driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local d
In camera driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial
In wlan driver, there is a possible missing bounds check, This could lead to local denial of service in wlan services.
In wlan driver, there is a possible missing bounds check, This could lead to local denial of service in wlan services.
In wlan driver, there is a possible missing bounds check, This could lead to local denial of service in wlan services.
wasm3 commit 7890a2097569fde845881e0b352d813573e371f9 was discovered to contain a segmentation fault via the component o
There is an Out-of-bounds write vulnerability in the AOD module in smartphones. Successful exploitation of this vulnerab
JHEAD is a simple command line tool for displaying and some manipulation of EXIF header data embedded in Jpeg images fro
A call stack overflow bug in the SAML login feature in Mattermost server in versions up to and including 6.3.2 allows an
Heap buffer overflow issues were found in Opensc before version 0.22.0 in pkcs15-oberthur.c that could potentially crash
Stack buffer overflow issues were found in Opensc before version 0.22.0 in various places that could potentially crash p
In Bender/ebee Charge Controllers in multiple versions a long URL could lead to webserver crash. The URL is used as inpu
A vulnerability was found in Sricam IP CCTV Camera and classified as critical. This issue affects some unknown processin
A vulnerability was found in Sricam IP CCTV Camera. It has been classified as critical. Affected is an unknown function
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