Directory Traversal Affecting filebrowser package, versions <2.32.0-r7


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.14% (35th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Directory Traversal vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-FILEBROWSER-9788775
  • published21 Apr 2025
  • disclosed13 Apr 2025

Introduced: 13 Apr 2025

CVE-2025-3445  (opens in a new tab)
CWE-22  (opens in a new tab)

How to fix?

Upgrade Chainguard filebrowser to version 2.32.0-r7 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream filebrowser package and not the filebrowser package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

A Path Traversal "Zip Slip" vulnerability has been identified in mholt/archiver in Go. This vulnerability allows using a crafted ZIP file containing path traversal symlinks to create or overwrite files with the user's privileges or application utilizing the library.

When using the archiver.Unarchive functionality with ZIP files, like this: archiver.Unarchive(zipFile, outputDir),  A crafted ZIP file can be extracted in such a way that it writes files to the affected system with the same privileges as the application executing this vulnerable functionality. Consequently, sensitive files may be overwritten, potentially leading to privilege escalation, code execution, and other severe outcomes in some cases.

It's worth noting that a similar vulnerability was found in TAR files (CVE-2024-0406). Although a fix was implemented, it hasn't been officially released, and the affected project has since been deprecated. The successor to mholt/archiver is a new project called mholt/archives, and its initial release (v0.1.0) removes the Unarchive() functionality.