Show filters
82 Total Results
Displaying 71-80 of 82
Sort by:
Attacker Value
Unknown

CVE-2023-35957

Disclosure Date: January 08, 2024 (last updated January 12, 2024)
Multiple heap-based buffer overflow vulnerabilities exist in the fstReaderIterBlocks2 VCDATA parsing functionality of GTKWave 3.3.115. A specially-crafted .fst file can lead to arbitrary code execution. A victim would need to open a malicious file to trigger these vulnerabilities.This vulnerability concerns the decompression function `uncompress`.
Attacker Value
Unknown

CVE-2023-35956

Disclosure Date: January 08, 2024 (last updated January 12, 2024)
Multiple heap-based buffer overflow vulnerabilities exist in the fstReaderIterBlocks2 VCDATA parsing functionality of GTKWave 3.3.115. A specially-crafted .fst file can lead to arbitrary code execution. A victim would need to open a malicious file to trigger these vulnerabilities.This vulnerability concerns the decompression function `fastlz_decompress`.
Attacker Value
Unknown

CVE-2023-35955

Disclosure Date: January 08, 2024 (last updated January 12, 2024)
Multiple heap-based buffer overflow vulnerabilities exist in the fstReaderIterBlocks2 VCDATA parsing functionality of GTKWave 3.3.115. A specially-crafted .fst file can lead to arbitrary code execution. A victim would need to open a malicious file to trigger these vulnerabilities.This vulnerability concerns the decompression function `LZ4_decompress_safe_partial`.
Attacker Value
Unknown

CVE-2023-35704

Disclosure Date: January 08, 2024 (last updated January 17, 2024)
Multiple stack-based buffer overflow vulnerabilities exist in the FST LEB128 varint functionality of GTKWave 3.3.115. A specially crafted .fst file can lead to arbitrary code execution. A victim would need to open a malicious file to trigger these vulnerabilities.This vulnerability concerns the fstReaderVarint32WithSkip function.
Attacker Value
Unknown

CVE-2023-35703

Disclosure Date: January 08, 2024 (last updated January 17, 2024)
Multiple stack-based buffer overflow vulnerabilities exist in the FST LEB128 varint functionality of GTKWave 3.3.115. A specially crafted .fst file can lead to arbitrary code execution. A victim would need to open a malicious file to trigger these vulnerabilities.This vulnerability concerns the fstReaderVarint64 function.
Attacker Value
Unknown

CVE-2023-35702

Disclosure Date: January 08, 2024 (last updated January 17, 2024)
Multiple stack-based buffer overflow vulnerabilities exist in the FST LEB128 varint functionality of GTKWave 3.3.115. A specially crafted .fst file can lead to arbitrary code execution. A victim would need to open a malicious file to trigger these vulnerabilities.This vulnerability concerns the fstReaderVarint32 function.
Attacker Value
Unknown

CVE-2023-35128

Disclosure Date: January 08, 2024 (last updated January 17, 2024)
An integer overflow vulnerability exists in the fstReaderIterBlocks2 time_table tsec_nitems functionality of GTKWave 3.3.115. A specially crafted .fst file can lead to memory corruption. A victim would need to open a malicious file to trigger this vulnerability.
Attacker Value
Unknown

CVE-2023-35057

Disclosure Date: January 08, 2024 (last updated January 17, 2024)
An integer overflow vulnerability exists in the LXT2 lxt2_rd_trace value elements allocation functionality of GTKWave 3.3.115. A specially crafted .lxt2 file can lead to memory corruption. A victim would need to open a malicious file to trigger this vulnerability.
Attacker Value
Unknown

CVE-2023-35004

Disclosure Date: January 08, 2024 (last updated January 17, 2024)
An integer overflow vulnerability exists in the VZT longest_len value allocation functionality of GTKWave 3.3.115. A specially crafted .vzt file can lead to arbitrary code execution. A victim would need to open a malicious file to trigger this vulnerability.
Attacker Value
Unknown

CVE-2023-34436

Disclosure Date: January 08, 2024 (last updated January 17, 2024)
An out-of-bounds write vulnerability exists in the LXT2 num_time_table_entries functionality of GTKWave 3.3.115. A specially crafted .lxt2 file can lead to arbitrary code execution. A victim would need to open a malicious file to trigger this vulnerability.