Vulnerabilities > Out-of-bounds Write
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-03-19 | CVE-2024-2615 | Out-of-bounds Write vulnerability in Mozilla Firefox Memory safety bugs present in Firefox 123. | 9.8 |
| 2024-03-19 | CVE-2024-2616 | Out-of-bounds Write vulnerability in Mozilla Firefox To harden ICU against exploitation, the behavior for out-of-memory conditions was changed to crash instead of attempt to continue. | 2.7 |
| 2024-03-19 | CVE-2024-22453 | Out-of-bounds Write vulnerability in Dell products Dell PowerEdge Server BIOS contains a heap-based buffer overflow vulnerability. | 6.0 |
| 2024-03-19 | CVE-2024-25942 | Out-of-bounds Write vulnerability in Dell products Dell PowerEdge Server BIOS contains an Improper SMM communication buffer verification vulnerability. | 6.8 |
| 2024-03-18 | CVE-2024-2581 | Out-of-bounds Write vulnerability in Tenda Ac10 Firmware 16.03.10.13 A vulnerability was found in Tenda AC10 16.03.10.13 and classified as critical. | 8.8 |
| 2024-03-18 | CVE-2023-52159 | Out-of-bounds Write vulnerability in multiple products A stack-based buffer overflow vulnerability in gross 0.9.3 through 1.x before 1.0.4 allows remote attackers to trigger a denial of service (grossd daemon crash) or potentially execute arbitrary code in grossd via crafted SMTP transaction parameters that cause an incorrect strncat for a log entry. | 7.5 |
| 2024-03-17 | CVE-2024-2558 | Out-of-bounds Write vulnerability in Tenda Ac18 Firmware 15.03.05.05 A vulnerability was found in Tenda AC18 15.03.05.05. | 8.8 |
| 2024-03-17 | CVE-2024-2547 | Out-of-bounds Write vulnerability in Tenda Ac18 Firmware 15.03.05.05 A vulnerability was found in Tenda AC18 15.03.05.05 and classified as critical. | 8.8 |
| 2024-03-17 | CVE-2024-2546 | Out-of-bounds Write vulnerability in Tenda Ac18 Firmware 15.13.07.09 A vulnerability has been found in Tenda AC18 15.13.07.09 and classified as critical. | 8.8 |
| 2024-03-15 | CVE-2021-47132 | Out-of-bounds Write vulnerability in Linux Kernel In the Linux kernel, the following vulnerability has been resolved: mptcp: fix sk_forward_memory corruption on retransmission MPTCP sk_forward_memory handling is a bit special, as such field is protected by the msk socket spin_lock, instead of the plain socket lock. Currently we have a code path updating such field without handling the relevant lock: __mptcp_retrans() -> __mptcp_clean_una_wakeup() Several helpers in __mptcp_clean_una_wakeup() will update sk_forward_alloc, possibly causing such field corruption, as reported by Matthieu. Address the issue providing and using a new variant of blamed function which explicitly acquires the msk spin lock. | 7.1 |