In the summer this year, Google experts, using the ClusterFuzz and OSS-Fuzz tools, discovered a dangerous bug in the Libarchive library. This vulnerability in Libarchive threatens many Linux distributions.The vulnerability impacts Libarchive, a library for reading and creating compressed files. It is a powerful all-in-one toolkit for working with archive files that also bundles other Linux/BSD utilities like tar, cpio, and cat, making it ideal for a wide variety of operations, and the reason it’s so widely adopted across operating systems.
Libarchive is included by default with Debian, Ubuntu, Gentoo, Arch Linux, FreeBSD, and NetBSD, and the vulnerability allows an attacker to execute arbitrary code on a vulnerable machine.
It is reported that Windows and macOS, which include the library, are not vulnerable.
“Thankfully, Windows and macOS, today’s two most popular operating systems are not impacted; otherwise, the bug would have caused major headaches to users all over the world”, — report ZDNet magazine journalists.
The bug received the identifier CVE-2019-18408. It allows an attacker to execute arbitrary code in the system using a specially created archive file. The problem can be exploited through a malicious file obtained from cybercriminals through local applications that use various components of Libarchive in their work.
Information about the problem was released only recently, after the release of patches for Linux and FreeBSD. Vulnerability is already fixed in Libarchive version 3.4.0. Most Linux distributions have already fixed the problem.
“The list of vulnerable operating systems and software utilities that ship Libarchive is exhaustive, opening a huge attack surface for malicious threat actors”, — write ZDNet journalists.
GitHub has published a list of vulnerable operating systems and applications, which includes desktop and server operating systems, package managers, security utilities, file browsers and so on, including well-known names such as pkgutils, Pacman, CMake, Nautilus and Samba.
At this stage, nothing is known about any public exploit code to test this vulnerability or about attempts to exploit it in the wild.