Fdu-Sec

**Name of the Vulnerable Software and Affected Versions** libheif version 1.17.5 **Description** The issue is related to a segmentation violation in the `UncompressedImageCodec::get luma bits per pixel from configuration unci()` function of the libheif decoder and encoder. This could allow a remote attacker to cause a denial of service. **Recommendations** For libheif version 1.17.5, consider disabling the `UncompressedImageCodec::get luma bits per pixel from configuration unci()` 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** libheif version 1.17.5 **Description** The issue is related to a segmentation violation in the `UncompressedImageCodec::decode uncompressed image()` function. This could potentially allow a remote attacker to impact the confidentiality, integrity, and availability of protected information. **Recommendations** For libheif version 1.17.5, consider disabling the `UncompressedImageCodec::decode uncompressed image()` function as a temporary workaround until a patch is available.

**Name of the Vulnerable Software and Affected Versions** libheif version 1.17.5 **Description** The issue is related to a segmentation error in the `find exif tag()` function of the libheif decoder and encoder for file formats. Exploitation of this issue could allow a remote attacker to impact the confidentiality, integrity, and availability of protected information. The vulnerability is caused by a segmentation violation via the `find exif tag()` function at `/libheif/exif.cc`. **Recommendations** For libheif version 1.17.5, as a temporary workaround, consider disabling the `find exif tag()` function 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** libheif version 1.17.5 **Description** The issue is related to a segmentation error in the /libheif/exif.cc component of the libheif decoder and encoder for file formats. Exploitation of this issue could allow a remote attacker to impact the confidentiality, integrity, and availability of protected information. The component /libheif/exif.cc is specifically mentioned as the source of the segmentation violation. **Recommendations** For libheif version 1.17.5, consider disabling the /libheif/exif.cc component 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.14 **Description** The issue is related to a global buffer overflow vulnerability in the `read coding unit` function at `slice.cc`. This vulnerability may allow a remote attacker to impact the confidentiality, integrity, and availability of protected information. **Recommendations** For Libde265 version 1.0.14, consider disabling the `read coding unit` 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.14 **Description** The issue is related to a heap-buffer-overflow vulnerability in the `derive spatial luma vector prediction` function. This vulnerability may allow a remote attacker to impact the confidentiality, integrity, and availability of protected information. The vulnerability is associated with the Libde265 video codec implementation of the h.265 standard. **Recommendations** For Libde265 version 1.0.14, consider disabling the `derive spatial luma vector prediction` function as a temporary workaround until a patch is available. Restrict access to the `motion.cc` file to minimize the risk of exploitation. Avoid using the vulnerable function in the affected video codec implementation until the issue is resolved. 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.14 **Description** The issue is related to a heap-buffer-overflow vulnerability in the `derive combined bipredictive merging candidates` function at `motion.cc`. This vulnerability may allow a remote attacker to impact the confidentiality, integrity, and availability of protected information. **Recommendations** For Libde265 version 1.0.14, consider disabling the `derive combined bipredictive merging candidates` 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.

**Nome do software vulnerável e versões afetadas** Libde265 versão 1.0.8 **Descrição** O problema está relacionado a um estouro de buffer de heap na função `ff hevc put hevc epel pixels 8 sse`, que pode ser explorado por invasores para causar uma negação de serviço (DoS) por meio de um arquivo de vídeo malicioso. Essa vulnerabilidade está associada à implementação do codec de vídeo Libde265. **Recomendações** Para a versão 1.0.8 do Libde265, atualize para a versão 1.0.11 para corrigir o problema de segurança. Como solução alternativa temporária, considere desativar a função `ff hevc put hevc epel pixels 8 sse` até que um patch esteja disponível.

**Nome do software vulnerável e versões afetadas** Libde265 versão 1.0.8 **Descrição** O problema está relacionado a uma vulnerabilidade de estouro de buffer na pilha (heap buffer overflow) na função `put epel 16 fallback()` da implementação do codec de vídeo Libde265 para h.265. Essa vulnerabilidade pode ser explorada por um invasor remoto usando um arquivo de vídeo especialmente criado, podendo levar a uma negação de serviço (DoS). A vulnerabilidade é causada pela função `put epel 16 fallback()` em `fallback-motion.cc`. **Recomendações** Para a versão 1.0.8 do Libde265, atualize para a versão 1.0.11 para corrigir os problemas de segurança. Como solução temporária, considere restringir o uso da função `put epel 16 fallback()` em `fallback-motion.cc` até que um patch esteja disponível. Evite usar arquivos de vídeo criados especificamente para explorar essa vulnerabilidade.