See how nanazip compares to other vendors in security performance
NanaZip is an open source file archive. Starting in version 5.0.1252.0 and prior to version 6.0.1630.0, circular NextOffset chains cause an infinite loop in the ROMFS archive parser. Version 6.0.1630.0 patches the issue.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip is an open source file archive Starting in version 5.0.1252.0 and prior to version 6.0.1630.0, NanaZip has an out-of-bounds heap read in .NET Single File bundle header parser due to missing bounds check. Opening a crafted file with NanaZip causes a crash or leaks heap data to the user. Version 6.0.1630.0 patches the issue.
NanaZip is an open source file archive. Starting in version 5.0.1252.0 and prior to versions 6.0.1638.0 and 6.5.1638.0, a memory corruption vulnerability in NanaZip’s UFS parser allows a crafted .ufs/.ufs2/.img file to trigger out-of-bounds memory access during archive open/listing. The bug is reachable via normal user file-open flow and can cause process crash, hang, and potentially exploitable heap corruption. Versions 6.0.1638.0 and 6.5.1638.0 fix the issue.
NanaZip is an open source file archive. Starting in version 5.0.1252.0 and prior to versions 6.0.1638.0 and 6.5.1638.0, NanaZip’s .NET Single File Application parser has an out-of-bounds read vulnerability in manifest parsing. A crafted bundle can provide a malformed RelativePathLength so the parser constructs a std::string from memory beyond HeaderBuffer, leading to crash and potential in-process memory disclosure. Versions 6.0.1638.0 and 6.5.1638.0 fix the issue.
NanaZip is an open source file archive Starting in version 5.0.1252.0 and prior to version 6.0.1630.0, circular NextOffset chains cause an infinite loop, and deeply nested directories cause unbounded recursion (stack overflow) in the ROMFS archive parser. Version 6.0.1630.0 patches the issue.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip is an open source file archive. Starting in version 5.0.1252.0 and prior to versions 6.0.1638.0 and 6.5.1638.0, a denial-of-service vulnerability exists in NanaZip’s .NET Single File Application parser. A crafted bundle can force an integer underflow in header-size calculation and trigger an unbounded memory allocation attempt during archive open. Versions 6.0.1638.0 and 6.5.1638.0 fix the issue.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip is the 7-Zip derivative intended for the modern Windows experience. Prior to 6.5.1749.0, NanaZip's UFS and FFS image handler in NanaZip.Codecs.Archive.Ufs.cpp validates the superblock block size only against the MINBSIZE lower bound and does not validate the fsfsize fragment size, allowing attacker-controlled 32-bit fields to flow into indirect-block, directory, and extraction buffer allocations. A tiny crafted UFS image can force multi-gigabyte allocations during open or extraction, causing memory exhaustion or process termination. This issue is fixed in version 6.5.1749.0.
NanaZip is the 7-Zip derivative intended for the modern Windows experience. Prior to 6.5.1749.0, NanaZip's seven in-house IInArchive handlers in NanaZip.Codecs unconditionally dereference the caller-supplied Indices array inside Extract when the archive engine signals extract everything by passing Indices as NULL and NumItems as 0xFFFFFFFF. This causes a NULL pointer dereference in the standard Test archive or Extract all code path for WebAssembly, ElectronAsar, Zealfs, Romfs, Ufs, Littlefs, and DotNetSingleFile archives, resulting in a process crash. This issue is fixed in version 6.5.1749.0.
NanaZip is the 7-Zip derivative intended for the modern Windows experience. Prior to 6.5.1749.0, NanaZip's WebAssembly archive handler in NanaZip.Codecs.Archive.WebAssembly.cpp allocates buffers from attacker-controlled 32-bit section and custom-name length fields without validating them against the data present in the file. A tiny crafted module can force multi-gigabyte allocations during listing or extraction through NameSize, Information.Size, and std::string or vector allocation paths, causing memory exhaustion or process termination. This issue is fixed in version 6.5.1749.0.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.
NanaZip contains memory-safety, parsing, and resource-exhaustion vulnerabilities that can cause memory corruption, information disclosure, or denial of service.