Vulnerabilities > Out-of-bounds Write
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-12-09 | CVE-2024-12352 | Out-of-bounds Write vulnerability in Totolink Ex1800T Firmware 9.1.0Cu.2112B20220316 A vulnerability classified as problematic was found in TOTOLINK EX1800T 9.1.0cu.2112_B20220316. | 9.8 |
| 2024-12-09 | CVE-2024-12354 | Out-of-bounds Write vulnerability in Razormist Phone Contact Manager System 1.0 A vulnerability, which was classified as critical, was found in SourceCodester Phone Contact Manager System 1.0. | 7.8 |
| 2024-12-08 | CVE-2024-12344 | Out-of-bounds Write vulnerability in Tp-Link Vn020 F3V Firmware 6.2.1021 A vulnerability, which was classified as critical, was found in TP-Link VN020 F3v(T) TT_V6.2.1021. | 9.8 |
| 2024-12-06 | CVE-2024-38922 | Out-of-bounds Write vulnerability in Openrobotics Robot Operating System 2 Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble version was discovered to contain a heap overflow in the nav2_amcl process. | 9.8 |
| 2024-12-06 | CVE-2024-53142 | Out-of-bounds Write vulnerability in Linux Kernel In the Linux kernel, the following vulnerability has been resolved: initramfs: avoid filename buffer overrun The initramfs filename field is defined in Documentation/driver-api/early-userspace/buffer-format.rst as: 37 cpio_file := ALGN(4) + cpio_header + filename + "\0" + ALGN(4) + data ... 55 ============= ================== ========================= 56 Field name Field size Meaning 57 ============= ================== ========================= ... 70 c_namesize 8 bytes Length of filename, including final \0 When extracting an initramfs cpio archive, the kernel's do_name() path handler assumes a zero-terminated path at @collected, passing it directly to filp_open() / init_mkdir() / init_mknod(). If a specially crafted cpio entry carries a non-zero-terminated filename and is followed by uninitialized memory, then a file may be created with trailing characters that represent the uninitialized memory. | 7.8 |
| 2024-12-05 | CVE-2018-9386 | Out-of-bounds Write vulnerability in Google Android In reboot_block_command of htc reboot_block driver, there is a possible stack buffer overflow due to a missing bounds check. | 6.7 |
| 2024-12-05 | CVE-2018-9391 | Out-of-bounds Write vulnerability in Google Android In update_gps_sv and output_vzw_debug of vendor/mediatek/proprietary/hardware/connectivity/gps/gps_hal/src/gpshal_wor ker.c, there is a possible out of bounds write due to a missing bounds check. | 6.7 |
| 2024-12-05 | CVE-2024-11156 | Out-of-bounds Write vulnerability in Rockwellautomation Arena An “out of bounds write” code execution vulnerability exists in the Rockwell Automation Arena® that could allow a threat actor to write beyond the boundaries of allocated memory in a DOE file. | 7.8 |
| 2024-12-05 | CVE-2018-9397 | Out-of-bounds Write vulnerability in Google Android In WMT_unlocked_ioctl of MTK WMT device driver, there is a possible OOB write due to a missing bounds check. | 6.7 |
| 2024-12-05 | CVE-2018-9398 | Out-of-bounds Write vulnerability in Google Android In fm_set_stat of mediatek FM radio driver, there is a possible OOB write due to improper input validation. | 6.7 |