Vulnerabilities > Out-of-bounds Read
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2024-10-29 | CVE-2024-50074 | Out-of-bounds Read vulnerability in multiple products In the Linux kernel, the following vulnerability has been resolved: parport: Proper fix for array out-of-bounds access The recent fix for array out-of-bounds accesses replaced sprintf() calls blindly with snprintf(). | 7.8 |
2024-10-28 | CVE-2024-44236 | Out-of-bounds Read vulnerability in Apple Macos An out-of-bounds access issue was addressed with improved bounds checking. | 5.5 |
2024-10-28 | CVE-2024-44281 | Out-of-bounds Read vulnerability in Apple Macos An out-of-bounds read was addressed with improved input validation. | 5.5 |
2024-10-28 | CVE-2024-44282 | Out-of-bounds Read vulnerability in Apple products An out-of-bounds read was addressed with improved input validation. | 5.5 |
2024-10-27 | CVE-2024-50612 | Out-of-bounds Read vulnerability in Libsndfile Project Libsndfile libsndfile through 1.2.2 has an ogg_vorbis.c vorbis_analysis_wrote out-of-bounds read. | 5.5 |
2024-10-25 | CVE-2024-47018 | Out-of-bounds Read vulnerability in Google Android In pmucal_rae_handle_seq_int of flexpmu_cal_rae.c, there is a possible out of bounds read due to a buffer overflow. | 5.5 |
2024-10-25 | CVE-2024-47019 | Out-of-bounds Read vulnerability in Google Android In ProtocolEmbmsSaiListAdapter::Init() of protocolembmsadapter.cpp, there is a possible out of bounds read due to a missing bounds check. | 5.5 |
2024-10-25 | CVE-2024-47021 | Out-of-bounds Read vulnerability in Google Android In sms_ExtractCbLanguage of sms_CellBroadcast.c, there is a possible out of bounds read due to a missing bounds check. | 7.5 |
2024-10-25 | CVE-2024-47026 | Out-of-bounds Read vulnerability in Google Android In gsc_gsa_rescue of gsc_gsa.c, there is a possible out of bounds read due to an incorrect bounds check. | 5.5 |
2024-10-25 | CVE-2024-47029 | Out-of-bounds Read vulnerability in Google Android In TrustySharedMemoryManager::GetSharedMemory of ondevice/trusty/trusty_shared_memory_manager.cc, there is a possible out of bounds read due to an incorrect bounds check. | 5.5 |