Symeon Paraschoudis

**Name of the Vulnerable Software and Affected Versions** Google Chrome versions prior to 145.0.7632.159 **Description** An integer overflow in the Skia graphics engine within Google Chrome versions prior to 145.0.7632.159 could allow a remote attacker to potentially perform out-of-bounds memory access through a specially crafted HTML page. The vulnerability resides in the Skia component. **Recommendations** Update Google Chrome to version 145.0.7632.159 or later.

Name of the Vulnerable Software and Affected Versions: Windows Trust Verification API (affected versions not specified) Description: The issue is related to a denial-of-service vulnerability in the Windows Trust Verification API, which is caused by resource release errors. This vulnerability can be exploited by a remote attacker to cause a denial of service. The estimated number of potentially affected devices worldwide is not available. There is no information about real-world incidents where this issue was exploited. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: Windows Remote Access (affected versions not specified) Description: The issue is related to an elevation of privilege vulnerability in Windows Remote Access, which occurs due to improper handling of memory. This can allow an attacker to elevate their privileges on the system. To exploit this vulnerability, an attacker would first need to gain execution on the victim system and then run a specially crafted application. The vulnerability is addressed by correcting how Windows Remote Access handles memory. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Windows Imaging API (affected versions not specified) **Description** The issue is related to the improper handling of objects in memory by the Windows Imaging API, which can be exploited to execute arbitrary code. This can be achieved by using a specially crafted .WIM file. The estimated number of potentially affected devices worldwide is not available. There is no information about real-world incidents where this issue was exploited. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Windows 7 Windows Server 2008 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 Windows Server 2019 Windows 8.1 Windows RT 8.1 Windows 10 Windows 10 Servers **Description** An information disclosure issue exists in the way the Windows Graphics Device Interface (GDI) handles objects in memory. This allows an attacker to retrieve information from a targeted system. The vulnerability can be exploited by using a specially crafted application to disclose protected information. **Recommendations** For Windows 7, update to a newer version to mitigate the risk. For Windows Server 2008, update to a newer version to mitigate the risk. For Windows Server 2008 R2, update to a newer version to mitigate the risk. For Windows Server 2012, update to a newer version to mitigate the risk. For Windows Server 2012 R2, update to a newer version to mitigate the risk. For Windows Server 2016, update to a newer version to mitigate the risk. For Windows Server 2019, update to a newer version to mitigate the risk. For Windows 8.1, update to a newer version to mitigate the risk. For Windows RT 8.1, update to a newer version to mitigate the risk. For Windows 10, update to a newer version to mitigate the risk. For Windows 10 Servers, update to a newer version to mitigate the risk.

**Name of the Vulnerable Software and Affected Versions** libcurl versions 7.17.1 through 7.38.0 **Description** The issue arises when using the `CURLOPT COPYPOSTFIELDS` option for HTTP POST transfers with libcurl. This option allows specifying a memory area holding the data to send to the remote server. However, the `curl easy duphandle` function does not properly copy this data for an easy handle, leading to an out-of-bounds read. This can allow remote web servers to read sensitive memory information. The problem occurs because the internal libcurl function that duplicates options from the old handle to the new mistakenly treats the post data buffer as a C string and uses `strdup()` to duplicate it, which can create a copy that is too small, too large, or can crash due to reading an inaccessible memory area. Furthermore, the pointer used to read from when sending the data is not updated after duplication of the handle data, causing libcurl to still read from the original handle's buffer, which could have been freed or reused. **Recommendations** For libcurl versions 7.17.1 through 7.38.0, consider disabling the `curl easy duphandle` function until a patch is available to prevent potential exploitation. Restrict access to the `CURLOPT COPYPOSTFIELDS` option to minimize the risk of sensitive data being sent unintentionally. Avoid using the `CURLOPT COPYPOSTFIELDS` option for HTTP POST transfers until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.