![]() ![]() Google demonstrated swift action by rolling out essential updates on its Stable and Extended stable channels. ![]() Try Free Demo Swift Responses from Major Browsers You can mitigate the risk and exposure of your organization’s SaaS applications in just a few simple steps. It’s an easy and efficient way to identify and manage risks. With DoControl, you can keep your SaaS applications and data safe and secure by creating workflows tailored to your needs. Start protecting your SaaS data in just a few minutes! Specifically, the flaw occurs when more memory is allocated if the table proves insufficiently large for valid data. The vulnerability’s root cause can be traced to the “BuildHuffmanTable” function, utilized to verify data accuracy. ![]() This underscores the urgency of addressing this issue promptly to prevent further exploitation and protect users from potential harm. Its advantages in size and speed, surpassing traditional formats like PNG and JPEG, have led to its widespread adoption.Ī user opening such a compromised image could trigger a heap buffer overflow within the content process, potentially leading to arbitrary code execution or system compromise. Google developed WebP, a modern image format celebrated for its superior lossless and lossy compression capabilities, making it ideal for web images. This image format is notably employed by popular browsers such as Google Chrome and Mozilla Firefox for its efficient image compression capabilities. This vulnerability poses a significant threat, as an attacker could exploit it through a malicious WebP image. The identified security vulnerability, assigned the identifier CVE-2023-4863, pertains to a heap buffer overflow in libwebp. This newly unearthed vulnerability, bearing the identifier CVE-2023-4863, has sent shockwaves through the cybersecurity community due to its potential for active exploitation. In a race against time to safeguard user security, major browser vendors, including Google and Mozilla, have scrambled to release urgent updates in response to a critical vulnerability discovered in the WebP Codec. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |