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 camera middleware, there is a possible out of bounds write due to a missing bounds check. This could lead to local es
In imgsys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In imgsys, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In hcp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In dpe, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In OPTEE, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In vdec, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of p
In IOMMU, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In wlan service, there is a possible out of bounds write due to improper input validation. This could lead to local esca
In wlan service, there is a possible out of bounds write due to improper input validation. This could lead to local esca
In wlan service, there is a possible out of bounds write due to improper input validation. This could lead to local esca
In wlan service, there is a possible out of bounds write due to improper input validation. This could lead to local esca
Memory corruption in RIL while trying to send apdu packet.
Memory corruption in WLAN while running doDriverCmd for an unspecific command.
Memory Corruption in GPS HLOS Driver when injectFdclData receives data with invalid data length.
Out-of-bounds Write in ReqDataRaw of libsec-ril prior to SMR Aug-2023 Release 1 allows local attacker to execute arbitra
Out-of-bounds Write in RmtUimApdu of libsec-ril prior to SMR Aug-2023 Release 1 allows local attacker to execute arbitra
Out-of-bounds Write in MakeUiccAuthForOem of libsec-ril prior to SMR Aug-2023 Release 1 allows local attacker to execute
Out-of-bounds Write in BuildOemEmbmsGetSigStrengthResponse of libsec-ril prior to SMR Aug-2023 Release 1 allows local at
Out-of-bounds Write in DoOemFactorySendFactoryBypassCommand of libsec-ril prior to SMR Aug-2023 Release 1 allows local a
Out-of-bounds Write in IpcTxPcscTransmitApdu of libsec-ril prior to SMR Aug-2023 Release 1 allows local attacker to exec
Out-of-bounds Write vulnerability in SSHDCPAPP TA prior to "SAMSUNG ELECTONICS, CO, LTD. - System Hardware Update -
Stack overflow vulnerability in SSHDCPAPP TA prior to "SAMSUNG ELECTONICS, CO, LTD. - System Hardware Update - 7/13
In gnss service, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalat
In nvram, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In netdagent, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation
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 gps, 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 gps, 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 seninf, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
In wlan driver, there is a possible out of bounds write due to improper input validation. This could lead to local escal
In connectivity system driver, there is a possible out of bounds write due to improper input validation. This could lead
In gnss service, there is a possible out of bounds write due to improper input validation. This could lead to local escl
Memory corruption in Audio during playback session with audio effects enabled.
Memory Corruption while accessing metadata in Display.
In video, there is a possible out of bounds write due to a permissions bypass. This could lead to local escalation of pr
In ftm, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In camera middleware, there is a possible out of bounds write due to a missing input validation. This could lead to loca
In camera middleware, there is a possible out of bounds write due to a missing input validation. This could lead to loca
In TVAPI, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of
Memory Corruption in VR Service while sending data using Fast Message Queue (FMQ).
In Bluetooth, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation
In Bluetooth, there is a possible out of bounds write due to improper input validation. This could lead to local escalat
In Bluetooth, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation
In display, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of p
In dpe, there is a possible out of bounds write due to a missing valid range checking. This could lead to local escalati
In dpe, there is a possible out of bounds write due to a missing valid range checking. This could lead to local escalati
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