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 (TBD) mprot_unmap? of (TBD), there is a possible way to corrupt the memory mapping due to improper input validation.
In widevine, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalati
In widevine, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalati
In widevine, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalati
In widevine, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalati
In keyinstall, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escala
In mpu, there is a possible memory corruption due to a logic error. This could lead to local escalation of privilege wit
In gz, there is a possible memory corruption due to a missing bounds check. This could lead to local escalation of privi
In display, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalatio
In display, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalatio
In isp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In isp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr
In Wi-Fi, there is a possible out of bounds write due to improper input validation. This could lead to local escalation
In Wi-Fi, there is a possible out of bounds write due to improper input validation. This could lead to local escalation
In ccci, there is a possible out of bounds write due to improper input validation. This could lead to local escalation o
In mapGrantorDescr of MessageQueueBase.h, there is a possible out of bounds write due to a missing bounds check. This co
In parameterToHal of Effect.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead
In getCurrentConfigImpl of Effect.cpp, there is a possible out of bounds write due to a missing bounds check. This could
In authToken2AidlVec of KeyMintUtils.cpp, there is a possible out of bounds write due to an incorrect bounds check. This
In _ufdt_output_strtab_to_fdt of ufdt_convert.c, there is a possible out of bounds write due to an incorrect bounds chec
In thermal_cooling_device_stats_update of thermal_sysfs.c, there is a possible out of bounds write due to improper input
In externalOnRequest of rilapplication.cpp, there is a possible out of bounds write due to a missing bounds check. This
In OemSimAuthRequest::encode of wlandata.cpp, there is a possible out of bounds write due to a missing bounds check. Thi
In RadioImpl::setGsmBroadcastConfig of ril_service_legacy.cpp, there is a possible stack clash leading to memory corrupt
In RadioImpl::setCdmaBroadcastConfig of ril_service_legacy.cpp, there is a possible stack clash leading to memory corrup
In ufdt_do_one_fixup of ufdt_overlay.c, there is a possible out of bounds write due to an incorrect bounds check. This c
In ppmp_unprotect_mfcfw_buf of drm_fw.c, there is a possible out of bounds write due to improper input validation. This
In updateStart of WirelessCharger.cpp, there is a possible out of bounds write due to a missing bounds check. This could
In sendChunk of WirelessCharger.cpp, there is a possible out of bounds write due to a missing bounds check. This could l
In HexString2Value of util.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead t
In FacilityLock::Parse of simdata.cpp, there is a possible out of bounds write due to a missing bounds check. This could
In ProtocolMiscBuilder::BuildSetLinkCapaReportCriteria of protocolmiscbuilder.cpp, there is a possible out of bounds wri
In CallDialReqData::encodeCallNumber of callreqdata.cpp, there is a possible out of bounds write due to an incorrect bou
In ProtocolMiscBuilder::BuildSetSignalReportCriteria of protocolmiscbuilder.cpp, there is a possible out of bounds write
In SimUpdatePbEntry::encode of simdata.cpp, there is a possible out of bounds write due to a missing bounds check. This
In ProtocolSimBuilder::BuildSimUpdatePb3gEntry of protocolsimbuilder.cpp, there is a possible out of bounds write due to
In ProtocolCallBuilder::BuildSendUssd of protocolcallbuilder.cpp, there is a possible out of bounds write due to a missi
In CallDialReqData::encode of callreqdata.cpp, there is a possible out of bounds write due to a missing bounds check. Th
In EmbmsSessionData::encode of embmsdata.cpp, there is a possible out of bounds write due to a missing bounds check. Thi
In ProtocolEmbmsBuilder::BuildSetSession of protocolembmsbuilder.cpp, there is a possible out of bounds write due to a m
In BroadcastSmsConfigsRequestData::encode of smsdata.cpp, there is a possible out of bounds write due to a missing bound
In CdmaBroadcastSmsConfigsRequestData::encode of cdmasmsdata.cpp, there is a possible stack clash leading to memory corr
In encode of wlandata.cpp, there is a possible out of bounds write due to improper input validation. This could lead to
In fillSetupDataCallInfo_V1_6 of ril_service_1_6.cpp, there is a possible out of bounds write due to an incorrect bounds
In fillSetupDataCallInfo_V1_6 of ril_service_1_6.cpp, there is a possible out of bounds write due to an incorrect bounds
In ConvertUtf8ToUcs2 of radio_hal_utils.cpp, there is a possible out of bounds write due to a missing bounds check. This
In phNxpNciHal_core_initialized of phNxpNciHal.cc, there is a possible out of bounds write due to a missing bounds check
vim is vulnerable to Heap-based Buffer Overflow
In preloader (usb), there is a possible out of bounds write due to a missing bounds check. This could lead to local esca
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