Leonzhao7

O problema está relacionado a um estouro de buffer de heap na função `mc chroma` da implementação do codec de vídeo libde265 para h.265. Isso pode ser explorado por um invasor remoto usando um arquivo especialmente criado, levando a uma negação de serviço. A função `mc chroma` é vulnerável a estouro de buffer, que pode ser acionado por meio de um arquivo criado para esse fim.

O problema está relacionado a um estouro de buffer de heap na função `ff hevc put unweighted pred 8 sse`. Isso pode ser explorado por meio de um arquivo malicioso, permitindo potencialmente que um invasor remoto acesse dados confidenciais, comprometa a integridade dos dados e cause uma negação de serviço.

The issue is related to a heap buffer overflow in the `mc luma` function of the libde265 video codec implementation. This can be exploited by a remote attacker using a specially crafted file, potentially leading to a denial of service.

The issue is related to a heap buffer overflow in the `put weighted bipred 16 fallback` function of the libde265 video codec implementation. This can be exploited by a remote attacker using a specially crafted file, potentially leading to a denial of service. The estimated number of potentially affected devices and details about real-world incidents are not provided.

The issue is related to a heap buffer overflow in the `put weighted pred avg 16 fallback` function of the libde265 video codec implementation. This can be exploited by a remote attacker using a specially crafted file, leading to a denial of service.

The issue is related to a heap buffer overflow in the `put qpel 0 0 fallback 16` function. This can be exploited by a remote attacker using a specially crafted file, potentially leading to a denial of service.

The issue is related to a segmentation fault in the `apply sao internal` function, which can be exploited via a crafted file, potentially allowing a remote attacker to cause a denial of service. The vulnerability is associated with a buffer overflow in memory.

The issue is related to a heap buffer overflow in the `put epel hv fallback` function, which can be exploited via a crafted file, potentially allowing a remote attacker to cause a denial of service.

The issue is related to a global buffer overflow in the `decode CABAC bit` function. This can be exploited via a crafted file, potentially allowing a remote attacker to cause a denial of service. The vulnerability is associated with the copying of a buffer without checking the input data.

The issue is related to a heap buffer overflow in the `de265 image::available zscan` function. This can be exploited via a crafted file, potentially allowing a remote attacker to cause a denial of service.

The issue is related to a stack buffer overflow in the `put qpel fallback` function. This can be exploited via a crafted file, potentially allowing a remote attacker to cause a denial of service.

The issue is related to a heap buffer overflow fault in the ` mm loadl epi64` function, which can be exploited via a crafted file, potentially allowing a remote attacker to cause a denial of service.

The issue is related to a heap buffer overflow fault in the `put epel 16 fallback` function. This can be exploited via a crafted file, potentially allowing a remote attacker to cause a denial of service.

The issue is related to a heap-based buffer over-read in the `process file` function, which can cause a denial of service, resulting in an application crash. This can be triggered by attackers using a crafted file.

The issue is related to a double free in the read MSAT function in ole.c, which can cause a denial of service, resulting in an application crash when a crafted file is processed.

The issue is related to an invalid free in the `read MSAT body` function in ole.c, which can be triggered by a crafted file. This is due to inconsistent memory management in the `ole2 read header` function. Attackers can cause a denial of service, leading to an application crash, or potentially have other unspecified impacts.

The issue is related to a heap-based buffer over-read in the getlong function in numutils.c, which can be exploited by attackers to cause a denial of service, resulting in an application crash. This can be achieved by providing a crafted file.

The issue is related to a NULL pointer dereference in the `igraph i strdiff` function within `igraph trie.c`, which can be exploited by attackers to cause a denial of service, resulting in an application crash. This can be achieved via a crafted object.

The issue allows attackers to cause a denial of service, specifically an infinite recursion, via a crafted file. This is related to the function `libfdata tree get node value` in `libfdata tree.c`.

Name of the Vulnerable Software and Affected Versions: libjpeg-turbo version 1.5.2 Description: The issue is related to a NULL Pointer Dereference in the `jdpostct.c` and `jquant1.c` components of the libjpeg-turbo library. This can be triggered by a crafted JPEG file, potentially allowing a remote attacker to cause a denial of service. Recommendations: For libjpeg-turbo version 1.5.2, consider avoiding the use of the `jdpostct.c` and `jquant1.c` components until a patch is available. As a temporary workaround, restrict the processing of specially crafted JPEG files to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.