Leonzhao7

**Nome do software vulnerável e versões afetadas** libde265 versão 1.0.4 **Descrição** 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. **Recomendações** Para a versão 1.0.4 da libde265, considere desativar a função `mc chroma` como uma solução temporária até que um patch esteja disponível. Restrinja o acesso à função vulnerável para minimizar o risco de exploração. Evite usar arquivos criados especificamente que possam acionar o estouro de buffer na função `mc chroma` até que o problema seja resolvido.

**Nome do software vulnerável e versões afetadas** libde265 versão 1.0.4 **Descrição** 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. **Recomendações** Para a libde265 versão 1.0.4, considere desativar a função `ff hevc put unweighted pred 8 sse` como uma solução temporária até que um patch esteja disponível. Restrinja o acesso a arquivos criados especificamente para explorar essa vulnerabilidade, a fim de minimizar o risco de exploração. No momento, não há informações sobre uma versão mais recente que contenha uma correção para essa vulnerabilidade.

**Name of the Vulnerable Software and Affected Versions** libde265 version 1.0.4 **Description** 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. **Recommendations** For libde265 version 1.0.4, consider disabling the `mc luma` function as a temporary workaround until a patch is available.

**Name of the Vulnerable Software and Affected Versions** libde265 version 1.0.4 **Description** 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. **Recommendations** For libde265 version 1.0.4, consider disabling the `put weighted bipred 16 fallback` function as a temporary workaround until a patch is available. Restrict the use of crafted files that could exploit this issue to minimize the risk of service disruption. 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** libde265 version 1.0.4 **Description** 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. **Recommendations** For libde265 version 1.0.4, consider disabling the `put weighted pred avg 16 fallback` function as a temporary workaround until a patch is available. Restrict access to the vulnerable function to minimize the risk of exploitation. Avoid using crafted files that could trigger the heap buffer overflow in the affected function. 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** libde265 version 1.0.4 **Description** 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. **Recommendations** For libde265 version 1.0.4, consider disabling the `put qpel 0 0 fallback 16` function as a temporary workaround until a patch is available. 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** libde265 version 1.0.4 **Description** 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. **Recommendations** For libde265 version 1.0.4, consider disabling the `apply sao internal` function as a temporary workaround until a patch is available. Restrict access to crafted files that could exploit this issue to minimize the risk of exploitation. 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** libde265 version v1.0.4 **Description** 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. **Recommendations** For libde265 version v1.0.4, consider disabling the `put epel hv fallback` function until a patch is available to prevent exploitation via crafted files.

**Name of the Vulnerable Software and Affected Versions** libde265 version 1.0.4 **Description** 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. **Recommendations** For libde265 version 1.0.4, consider disabling the `decode CABAC bit` function as a temporary workaround until a patch is available. Restrict access to files that could potentially exploit this issue to minimize the risk of exploitation. 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** libde265 version 1.0.4 **Description** 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. **Recommendations** For libde265 version 1.0.4, consider disabling the `de265 image::available zscan` function as a temporary workaround until a patch is available. Restrict access to files that could be used to exploit this issue to minimize the risk of exploitation. 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** libde265 version 1.0.4 **Description** 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. **Recommendations** For libde265 version 1.0.4, consider disabling the `put qpel fallback` function as a temporary workaround until a patch is available. Restrict access to crafted files that could exploit this issue to minimize the risk of exploitation. 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** libde265 version 1.0.4 **Description** 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. **Recommendations** For libde265 version 1.0.4, consider disabling the ` mm loadl epi64` function as a temporary workaround until a patch is available. Restrict access to crafted files that could exploit this issue to minimize the risk of exploitation. 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** libde265 version 1.0.4 **Description** 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. **Recommendations** For libde265 version 1.0.4, consider disabling the `put epel 16 fallback` function as a temporary workaround until a patch is available. Avoid using crafted files that could exploit this issue. 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** libdoc through 2017-10-23 **Description** 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. **Recommendations** For versions through 2017-10-23, consider avoiding the use of the `process file` function until a fix is available. As a temporary workaround, restrict the processing of files from untrusted sources to minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this issue.

**Name of the Vulnerable Software and Affected Versions** libxls version 1.4.0 **Description** 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. **Recommendations** For libxls version 1.4.0, 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** libxls version 1.4.0 **Description** 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. **Recommendations** For libxls version 1.4.0, 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** libdoc through 2017-10-23 **Description** 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. **Recommendations** For libdoc through 2017-10-23, consider updating to a version released after 2017-10-23 to resolve the issue. As a temporary workaround, restrict the processing of crafted files to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** igraph versions through 0.7.1 **Description** 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. **Recommendations** For versions through 0.7.1, consider updating to a patched version to mitigate this security risk. As a temporary workaround, consider taking necessary precautions to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** libpff versions prior to experimental-20180714 **Description** 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`. **Recommendations** For versions prior to experimental-20180714, update to a version that includes the fix for the infinite recursion issue in `libpff item tree create node`.

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.