[Bug 2051952] Update Released
Andreas Hasenack
2051952 at bugs.launchpad.net
Thu Feb 15 13:14:01 UTC 2024
The verification of the Stable Release Update for unzip has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to unzip in Ubuntu.
https://bugs.launchpad.net/bugs/2051952
Title:
unzip rejects Microsoft OneDrive zip files
Status in unzip package in Ubuntu:
Fix Released
Status in unzip source package in Focal:
Fix Released
Status in unzip source package in Jammy:
Fix Released
Status in unzip source package in Mantic:
Fix Released
Status in unzip source package in Noble:
Fix Released
Bug description:
[Impact]
unzip rejects Microsoft OneDrive zip files. See the detailed explanation here:
https://www.bitsgalore.org/2020/03/11/does-microsoft-onedrive-export-
large-ZIP-files-that-are-corrupt
tl;dr;
Microsoft mishandles the "Total number of disks" field when using the ZIP64 extension. It should start at 1, they use 0, which isn't a valid value. Unzip doesn't properly handle the invalid value.
[Test Plan]
- Download the test zip file from comment #1.
- unzip should extract it without issue (it contains a test.txt text file)
- if unzip fails, it will spew out a weird error message like the following:
$ unzip test.zip
Archive: test.zip
error [test.zip]: missing 4294967098 bytes in zipfile
(attempting to process anyway)
error [test.zip]: start of central directory not found;
zipfile corrupt.
(please check that you have transferred or created the zipfile in the
appropriate BINARY mode and that you have compiled UnZip properly)
[Where problems could occur]
This simple patch just accepts 0 as a valid total number of disks. I suppose if it was wrong it would mishandle multi-disk archives, though multi-disk archives should have a good value in that field.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/2051952/+subscriptions
More information about the foundations-bugs
mailing list