cpio in Busybox 1.27 ingnores "unsafe links"
Bug #1753572 reported by
Bryan Seitz
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
busybox (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Fix Released
|
Undecided
|
Unassigned | ||
debirf (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bionic |
Confirmed
|
Undecided
|
Unassigned | ||
Cosmic |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
busybox:
Installed: 1:1.27.2-2ubuntu3
Candidate: 1:1.27.2-2ubuntu3
3) Expected my CPIO archive to be fully extracted with proper symlinks
Command: unxz < /rootfs.cxz | cpio -i
4) 'Unsafe' symlinks were ignored such as:
sbin/init -> /lib/systemd/
With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly.
1.22 from Xenial works.
GNU Cpio also works.
It looks like 1.28 adds an env var to override this behavior:
libarchive: do not extract unsafe symlinks unless $EXTRACT_
CVE References
affects: | busybox → debirf (Ubuntu) |
Changed in debirf (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.