← back
CVE-2023-37460

Plexus Archiver vulnerable to Arbitrary File Creation in AbstractUnArchiver

CVSS 8.1 HIGHEPSS 2.1%CWE-22CWE-61
In short

Plexus Archiver has a flaw where extracting archive files can bypass security checks and write files to unintended locations on your system using symbolic links. This could allow attackers to create malicious files or run code on your computer if you extract an untrusted archive.

Technical detail

CVE-2023-37460 exploits a path traversal vulnerability in AbstractUnArchiver's resolveFile() function where broken symbolic links in the destination directory bypass directory traversal validation, allowing Files.newOutputStream() to write archive contents to arbitrary symlink targets outside the intended extraction directory. The attack vector requires a specially crafted archive with symlink entries and pre-existing broken symlinks in the target directory, enabling arbitrary file creation and potential RCE.

Summary generated and translated by AI from the official description.
Plexis Archiver is a collection of Plexus components to create archives or extract archives to a directory with a unified `Archiver`/`UnArchiver` API. Prior to version 4.8.0, using AbstractUnArchiver for extracting an archive might lead to an arbitrary file creation and possibly remote code execution. When extracting an archive with an entry that already exists in the destination directory as a symbolic link whose target does not exist - the `resolveFile()` function will return the symlink's source instead of its target, which will pass the verification that ensures the file will not be extracted outside of the destination directory. Later `Files.newOutputStream()`, that follows symlinks by default, will actually write the entry's content to the symlink's target. Whoever uses plexus archiver to extract an untrusted archive is vulnerable to an arbitrary file creation and possibly remote code execution. Version 4.8.0 contains a patch for this issue.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Want to know if your infrastructure is exposed to this?

Talk to TrueHacking →