PT-2022-29623

Name of the Vulnerable Software and Affected Versions Linux Kernel versions prior to v5.16.20 Description The issue is related to a read out of bounds error in the LZ4 decompress safe partial function. The actual impact and attack plausibility have not yet been proven. Recommendations For Linux...

PT-2022-29278

Name of the Vulnerable Software and Affected Versions Linux Kernel versions prior to v5.17.3 Description The issue is related to a read out of bounds error in the LZ4 decompress safe partial function. The actual impact and attack plausibility have not yet been proven. Recommendations For Linux...

PT-2022-30446

Name of the Vulnerable Software and Affected Versions lz4 versions prior to v5.4.189 Description The issue is related to a read out of bounds error in the LZ4 decompress safe partial function. The actual impact and attack plausibility have not yet been proven. Recommendations For versions prior t...

PT-2022-36935

Name of the Vulnerable Software and Affected Versions No specific software or versions are mentioned in the provided description. Description A crash has been reported, identified as a Stack-use-after-return READ 1 issue. The crash involves the std:: 1:: function:: func and...

grok:grk_decompress_fuzzer: Stack-use-after-return in std::__1::__function::__func<bool grk::WaveletReverse::decompress_partial_tile<i

Detailed Report: https://oss-fuzz.com/testcase?key=4738683825160192 Project: grok Fuzzing Engine: libFuzzer Fuzz Target: grkdecompressfuzzer Job Type: libfuzzerasangrok Platform Id: linux Crash Type: Stack-use-after-return READ 1 Crash Address: 0x7f55c11e0058 Crash State: std::1::function::funcbo...

PT-2022-36928

Name of the Vulnerable Software and Affected Versions No specific software or versions are mentioned in the provided description. Description A crash has been reported, identified as a Stack-use-after-scope WRITE 1 issue. The crash involves the grk::WaveletReverse::decompress partial tile functio...

PT-2022-36915

Name of the Vulnerable Software and Affected Versions No specific software or versions are mentioned in the provided description. Description The issue is related to a crash caused by an unknown read. The crash occurs in the decompress smooth data, process data simple main, and jpeg read scanline...

PT-2022-36918

Name of the Vulnerable Software and Affected Versions No specific software or versions are mentioned in the provided description. Description The issue is related to a heap-use-after-free READ 4 crash type. The crash state involves several function calls, including decode mcu, decompress onepass,...

OSV-2022-304 Heap-use-after-free in decode_mcu

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46335 Crash type: Heap-use-after-free WRITE 4 Crash state: decodemcu consumedata jpegstartdecompress...

PT-2022-36910

Name of the Vulnerable Software and Affected Versions No specific software or versions are mentioned in the provided description. Description The issue is related to a heap-use-after-free error, which occurs when the program attempts to access memory that has already been freed. The crash state...

PT-2022-36911

Name of the Vulnerable Software and Affected Versions No specific software or versions are mentioned in the provided description. Description The issue is related to a heap-use-after-free error, specifically a WRITE 4 crash type. The crash occurs in the following functions: decode mcu, consume...

c-blosc2:decompress_chunk_fuzzer: Crash in ZSTD_freeCCtx

Project: https://github.com/Blosc/c-blosc2.git Detailed Report: https://oss-fuzz.com/testcase?key=6597923997089792 Project: c-blosc2 Fuzzing Engine: libFuzzer Fuzz Target: decompresschunkfuzzer Job Type: libfuzzerubsanc-blosc2 Platform Id: linux Crash Type: UNKNOWN READ Crash Address:...

DEBIAN-CVE-2022-26291

lrzip v0.641 was discovered to contain a multiple concurrency use-after-free between the functions zpaqdecompressbuf and clearrulist. This vulnerability allows attackers to cause a Denial of Service DoS via a crafted Irz file...

PT-2022-7371

Name of the Vulnerable Software and Affected Versions lrzip version 0.641 Description The issue is related to a multiple concurrency use-after-free between the functions zpaq decompress buf and clear rulist. This allows attackers to cause a Denial of Service DoS via a crafted Irz file. The...

grok:grk_decompress_fuzzer: Use-of-uninitialized-value in grk::PacketLengthMarkers::readPLM

Project: https://github.com/GrokImageCompression/grok.git https://github.com/GrokImageCompression/grok-test-data.git Detailed Report: https://oss-fuzz.com/testcase?key=5755868006711296 Project: grok Fuzzing Engine: libFuzzer Fuzz Target: grkdecompressfuzzer Job Type: libfuzzermsangrok Platform Id...

CVE-2021-43304

Heap buffer overflow in Clickhouse's LZ4 compression codec when parsing a malicious query. There is no verification that the copy operations in the LZ4::decompressImpl loop and especially the arbitrary copy operation wildCopyop, ip, copyend, don’t exceed the destination buffer’s limits...

Heap overflow

A heap-based buffer overflow was found in openjpeg in color.c:379:42 in sycc420torgb when decompressing a crafted .j2k file. An attacker could use this to execute arbitrary code with the permissions of the application compiled against openjpeg...

grok:grk_decompress_fuzzer: Use-of-uninitialized-value in unsigned long grk::N_AVX2::vscheduler<grk::N_AVX2::DecompressDcShiftIrrev>

Project: https://github.com/GrokImageCompression/grok.git https://github.com/GrokImageCompression/grok-test-data.git Detailed Report: https://oss-fuzz.com/testcase?key=5434885018353664 Project: grok Fuzzing Engine: libFuzzer Fuzz Target: grkdecompressfuzzer Job Type: libfuzzermsangrok Platform Id...

OSV-2022-128 Stack-buffer-overflow in decompress_rNUMBER

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=44432 Crash type: Stack-buffer-overflow WRITE 1 Crash state: decompressrNUMBER readrNUMBERmetadata dwgdecode...

PT-2022-36818

Name of the Vulnerable Software and Affected Versions No specific software or versions are mentioned in the provided descriptions. Description The issue is related to a stack-buffer-overflow crash, specifically a WRITE 1 type. The crash occurs in the decompress rNUMBER, read rNUMBER meta data, an...