Memory corruption in Linux while sending DRM request.
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 wlan, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p
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 preloader, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation
In wlan, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disc
In vcu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In vcu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In vcu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In vcu, there is a possible memory corruption due to a logic error. This could lead to local escalation of privilege wit
In vcu, there is a possible memory corruption due to a logic error. This could lead to local escalation of privilege wit
In swpm, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p
In keymange, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation
In keymange, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation
Tenda AC10 v4 US_AC10V4.0si_V16.03.10.13_cn was discovered to contain a stack overflow via parameter list at /goform/Set
Tenda AC10 v4 US_AC10V4.0si_V16.03.10.13_cn was discovered to contain a stack overflow via parameter time at /goform/Pow
Tenda AC10 v4 US_AC10V4.0si_V16.03.10.13_cn was discovered to contain a stack overflow via parameter list at /goform/Set
Tenda AC10 v4 US_AC10V4.0si_V16.03.10.13_cn was discovered to contain a stack overflow via parameter devName at /goform/
Tenda AC10 v4 US_AC10V4.0si_V16.03.10.13_cn was discovered to contain a stack overflow via parameter shareSpeed at /gofo
A out-of-bounds write in Fortinet FortiOS version 7.2.0 through 7.2.3, FortiOS version 7.0.0 through 7.0.10, FortiOS ver
In the Google BMS kernel module, there is a possible out of bounds write due to a heap buffer overflow. This could lead
In encode of wlandata.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to loc
In Parse of simdata.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead to local
In Parse of simdata.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead to local
In load_dt_data of storage.c, there is a possible out of bounds write due to a missing bounds check. This could lead to
In aoc_service_set_read_blocked of aoc.c, there is a possible out of bounds write due to a missing bounds check. This co
In rpmb, there is a possible out of bounds write due to a logic error. This could lead to local escalation of privilege
In keyinstall, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation o
In cmdq, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p
In apu, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In ril, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In gps, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In pqframework, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalati
In display, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation o
Memory Corruption in Linux while processing QcRilRequestImsRegisterMultiIdentityMessage request.
Memory Corruption in Data Network Stack & Connectivity when sim gets detected on telephony.
Memory corruption in Linux while calling system configuration APIs.
Memory corruption in Audio while processing sva_model_serializer using memory size passed by HIDL client.
Memory corruption in Linux when the file upload API is called with parameters having large buffer.
Out of bounds read and write in callrunTspCmd of sysinput HAL service prior to SMR Jul-2023 Release 1 allows local attac
Out of bounds read and write in callgetTspsysfs of sysinput HAL service prior to SMR Jul-2023 Release 1 allows local att
Out of bounds read and write in callrunTspCmdNoRead of sysinput HAL service prior to SMR Jul-2023 Release 1 allows local
Out of bounds read and write in enableTspDevice of sysinput HAL service prior to SMR Jul-2023 Release 1 allows local att
Out-of-bounds Write in BuildOemSecureSimLockResponse of libsec-ril prior to SMR Jul-2023 Release 1 allows local attacker
Out-of-bounds Write in DoOemFactorySendFactoryTestResult of libsec-ril prior to SMR Jul-2023 Release 1 allows local atta
Out-of-bounds Write in BuildIpcFactoryDeviceTestEvent of libsec-ril prior to SMR Jul-2023 Release 1 allows local attacke
IBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Server) 11.5 with a Federated configuration is vulnerable to a
In keyinstall, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalatio
In keyinstall, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalatio
In gps, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
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