In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac there is a possible out of bounds write to missing bounds check. This could lead to remote code execution wit
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execut
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libxaac there is a possible out of bounds write due to a missing bounds check. This could lead to remote code executi
In libmediaextractor there is a possible out of bounds write due to an integer overflow. This could lead to remote code
In MPEG4Extractor, there is a possible out of bounds write due to an integer overflow. This could lead to remote code ex
In libexif, there is a possible out of bounds write due to an integer overflow. This could lead to remote escalation of
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In libFDK, there is a possible out of bounds write due to an integer overflow. This could lead to remote code execution
In libMpegTPDec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code exec
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In libMpegTPDec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code exec
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In libFDK, there is a possible out of bounds write due to an integer overflow. This could lead to remote code execution
In libstagefright, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote code
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In Bluetooth, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code exec
In libeffects, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code exe
In libAACdec, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi
In PV_DecodePredictedIntraDC of dec_pred_intra_dc.cpp, there is a possible out of bounds write due to a missing bounds c
In VlcDequantH263IntraBlock_SH of vlc_dequant.cpp, there is a possible out of bounds write due to a missing bounds check
In GetMBheader of combined_decode.cpp, there is a possible out of bounds write due to a missing bounds check. This could
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