Antti Levomäki

Um problema de double free existe que permite a um invasor não autorizado executar código arbitrário através de uma rede, afetando potencialmente o sistema. Um double free ocorre quando o programa tenta liberar o mesmo local de memória duas vezes, o que pode levar à corrupção de memória.

Nome do software vulnerável e versões afetadas: WithSecure Atlant (anteriormente F-Secure Atlant) versão 1.0.35-1 Descrição: A vulnerabilidade permite um ataque remoto de negação de serviço devido à corrupção de memória durante a verificação de um arquivo PE32. Recomendações: Para a versão 1.0.35-1, considere desativar a verificação de arquivos PE32 até que uma correção esteja disponível. No momento, não há informações sobre uma versão mais recente que contenha uma correção para essa vulnerabilidade.

The issue allows a Denial of Service (DoS) in the antivirus engine when scanning a fuzzed PE32 file.

Foi descoberta uma vulnerabilidade de negação de serviço (DoS) no componente fsicapd utilizado em determinados produtos da F-Secure. Ao verificar pacotes maiores ou arquivos submetidos a testes de fuzzing, o componente consome memória em excesso, o que pode eventualmente causar a falha do mecanismo de verificação. Essa vulnerabilidade pode ser explorada remotamente por um invasor.

O problema está relacionado a um estouro de buffer de heap no manipulador de conteúdo PDF PDFium. Ele pode ser explorado por um invasor remoto por meio de uma página HTML especialmente criada, podendo levar à corrupção do heap.

The issue concerns a buffer over-read in the BGP parser component of tcpdump, specifically in the `bgp attr print()` function within `print-bgp.c`. This could allow a remote attacker to obtain sensitive information by sending a specially crafted request.

The issue concerns a buffer over-read in the telnet parser, specifically in the `telnet parse()` function within `print-telnet.c`. This could allow a remote attacker to obtain sensitive information by sending a specially crafted request.

The issue is related to a bug in the RESP parser, specifically in the `resp get length()` function within `print-resp.c`, which could cause an infinite loop. Additionally, there is a buffer overread memory issue in the HNCP component that could allow a remote attacker to obtain sensitive information by sending a specially crafted request.

The issue is related to the ISAKMP parser in tcpdump, which could enter an infinite loop due to bugs in print-isakmp.c, affecting several functions. Additionally, it could allow a remote attacker to obtain sensitive information by exploiting a buffer overread memory in the HNCP component. This can be achieved by sending a specially crafted request.

The issue concerns a buffer over-read in the BGP parser, specifically within the `bgp attr print()` function in `print-bgp.c`. This problem affects the tcpdump tool.

The issue is related to the DNS parser in tcpdump, which could enter an infinite loop due to a bug in the `ns print()` function. This is caused by a flaw in the `print-domain.c` file. Additionally, there is a buffer overread memory issue in the HNCP component that could allow a remote attacker to obtain sensitive information by sending a specially crafted request.

The issue concerns a buffer over-read in the PIMv2 parser, specifically within the `pimv2 print()` function located in print-pim.c. This problem affects the tcpdump analyzer.

The issue is related to a bug in the LLDP parser, which could cause an infinite loop due to a problem in the `lldp private 8021 print()` function. This could potentially allow a remote attacker to obtain sensitive information by sending a specially crafted request, exploiting a buffer overread memory issue in the HNCP component.

The issue is related to a buffer over-read in the IS-IS parser, specifically in the `isis print extd ip reach()` function within `print-isoclns.c`. This problem can lead to potential security issues.

The issue is related to a buffer over-read in the IS-IS parser, specifically in the `isis print()` function within `print-isoclns.c`. This problem can lead to potential security issues due to the over-read of buffer data.

The issue is related to a buffer over-read in the IEEE 802.15.4 parser, specifically in the print-802 15 4.c:ieee802 15 4 if print() function. This problem affects the tcpdump protocol analyzer.

The issue is related to a buffer over-read in the LMP parser, specifically in the `lmp print()` function within the print-lmp.c file. This problem can lead to potential data exposure or crashes.

The issue is related to a buffer over-read in the Juniper protocols parser, specifically in the `juniper parse header()` function within `print-juniper.c`. This affects the tcpdump protocol analyzer.

The issue is related to a buffer over-read in the SMB/CIFS parser of tcpdump, which could allow a remote attacker to obtain sensitive information. This can be achieved by sending a specially crafted request to exploit the buffer overread memory in the HNCP component.

The issue is related to several protocol parsers that could cause a buffer over-read in the `lookup bytestring()` function. This could allow a remote attacker to obtain sensitive information by sending a specially crafted request, exploiting the buffer overread memory in the HNCP component.