Mark Brand

An out of bounds memory write when processing the AMD PSP1 Configuration Block (APCB) could allow an attacker with access to modify the BIOS image and potentially modify the APCB block, resulting in arbitrary code execution. This issue affects the AMD EPYC 7001 Processors.

The issue is related to a type confusion in the spellcheck service of Google Chrome and Microsoft Edge, allowing a remote attacker to potentially exploit heap corruption via a crafted HTML page. This could impact the confidentiality, integrity, and availability of protected information. The estimated number of potentially affected devices is not specified.

The issue is related to a heap buffer overflow in the Skia graphics library of Google Chrome, which can be exploited by a remote attacker using a specially crafted HTML page. This could potentially allow the attacker to execute arbitrary code, especially if the renderer process has been compromised.

The issue is related to an untrusted input stream being copied to a stack buffer without checking its size, resulting in a potentially exploitable crash that could lead to a sandbox escape. This could allow a remote attacker to bypass security restrictions and cause a denial of service. The vulnerability is also associated with a buffer overflow error in the StorageManager of Mozilla Firefox, Firefox ESR, and Thunderbird, which could allow a remote attacker to execute arbitrary code on the target system by tricking the victim into opening a specially crafted website.

The issue is related to an out of bounds memory access in the Mojo library of Google Chrome, which can potentially allow a remote attacker to exploit heap corruption via a crafted HTML page. This could enable the attacker to execute arbitrary code. The attacker must have compromised the renderer process to potentially exploit this issue.

The issue is related to an inappropriate implementation in the Skia graphics library of Google Chrome, which can be exploited by a remote attacker to potentially perform a sandbox escape. This can be achieved via a crafted HTML page, assuming the renderer process has been compromised.

The issue is related to an out of bounds memory access in Mojo, a component of Google Chrome, which could allow a remote attacker to exploit heap corruption via a crafted HTML page. This could potentially lead to a denial of service or the execution of arbitrary code.

The issue is related to an out of bounds read in the GPU Video component, which could allow a remote attacker to potentially exploit heap corruption via a crafted HTML page. This could lead to unauthorized access to protected information.

The issue is related to an out of bounds read in the ANGLE library of Google Chrome, which can be exploited by a remote attacker to potentially gain unauthorized access to protected information via a specially crafted HTML page. This can lead to heap corruption if the renderer process is compromised.

The issue is related to insufficient input validation in the SYS KEY DERIVE system call, which can be exploited by an attacker to corrupt AMD Secure Processor (ASP) OS memory, potentially leading to arbitrary code execution. This can occur in a compromised user application or ABL. The vulnerability is associated with the implementation of AMD Secure Processor (ASP) microcode in AMD processors.

The issue is related to insufficient input validation in the implementation of the SNP INIT command for the AMD processor firmware loading mode. This could allow a remote attacker to compromise the integrity of protected information. Additionally, failure to verify the CPU execution mode during SNP INIT may lead to potential memory integrity loss for SNP guests.

The issue is related to a use after free in Core, which can potentially allow a remote attacker to exploit heap corruption via a crafted HTML page. This could lead to arbitrary code execution. The vulnerability is associated with the use of memory after it has been freed, specifically in the base component of Google Chrome and Microsoft Edge browsers.

The issue is related to an out of bounds read in the compositing component of Google Chrome and Microsoft Edge, which can be exploited by a remote attacker who has compromised the renderer process. This could potentially allow the attacker to perform a sandbox escape via a crafted HTML page.

The issue is related to insufficient DRAM address validation, which may lead to a denial of service due to DMA read/write operations from/to invalid DRAM addresses.

The issue is related to the failure to flush the Translation Lookaside Buffer (TLB) of the I/O memory management unit (IOMMU), which may allow an IO device to write to memory it should not be able to access. This could result in a potential loss of integrity.

The issue is related to the failure to assign a new report ID to an imported guest, which may potentially result in an SEV-SNP guest VM being tricked into trusting a dishonest Migration Agent (MA).

A bug related to the SEV-ES TMR may cause a potential loss of memory integrity for SNP-active VMs.

The issue is caused by a heap buffer overflow in the WebGPU API, which can be exploited by a remote attacker who has compromised the renderer process. This can potentially lead to heap corruption via a crafted HTML page.

The issue is related to a heap buffer overflow in the WebGL component of Google Chrome, which could be exploited by a remote attacker via a crafted HTML page, potentially leading to heap corruption. This could result in a denial of service or allow the execution of arbitrary code.

The issue is related to the uninitialized use in the File API of Google Chrome, which could allow a remote attacker to potentially perform out of bounds memory access. This can be achieved via a crafted HTML page, allowing the attacker to bypass security restrictions.