![]() ![]() Heap buffer overflow in ANGLE in Google Chrome prior to 1.96 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. Heap buffer overflow in Skia in Google Chrome prior to 1.96 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. Heap buffer overflow in Mojom IDL in Google Chrome prior to 1.96 allowed a remote attacker who had compromised the renderer process and gained control of a WebUI process to potentially exploit heap corruption via a crafted HTML page. ![]() VP9 in libvpx before 1.13.1 mishandles widths, leading to a crash related to encoding. This issue has been fixed in CUPS version 2.4.7, released in September of 2023. This issue may lead to code execution.ĭue to failure in validating the length provided by an attacker-crafted PPD PostScript document, CUPS and libppd are susceptible to a heap-based buffer overflow and possibly code execution. Since there is another integer overflow an attacker may overflow it too to force `setup_malloc` to return 0 and make the exploit more reliable. This vulnerability affects Firefox ESR comment_list_length)` which may make `setup_malloc` allocate less memory than required. The `nsWindow::PickerOpen(void)` method was susceptible to a heap buffer overflow when running in headless mode. ![]() A perf_event's read_size can overflow, leading to an heap out-of-bounds increment or write in perf_read_group(). (Chromium security severity: High)Ī heap out-of-bounds write vulnerability in the Linux kernel's Performance Events system component can be exploited to achieve local privilege escalation. Heap buffer overflow in WebRTC in Google Chrome prior to 1.129 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |