Zarf: Symlink targets in archives are not validated against destination directory
zarf-dev zarf
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/zarf-dev/zarf/src/pkg/archive Go |
|
|
| github.com/zarf-dev/zarf Go |
|
|
zarf-dev zarf
| Product | Affected | Fixed in |
|---|---|---|
| github.com/zarf-dev/zarf/src/pkg/archive Go |
|
|
| github.com/zarf-dev/zarf Go |
|
|
Zarf is an Airgap Native Packager Manager for Kubernetes. From version 0.54.0 to before version 0.73.1, a path traversal vulnerability in archive extraction allows a specifically crafted Zarf package to create symlinks pointing outside the destination directory, enabling arbitrary file read or write on the system processing the package. This issue has been patched in version 0.73.1.
From the CVE record · GitHub_M
Zarf's archive extraction is vulnerable to path traversal. When a system processes a specially crafted Zarf package, the package can create symlinks outside the destination directory, enabling arbitrary file reads or writes.
Engineers using github.com/zarf-dev/zarf or github.com/zarf-dev/zarf/src/pkg/archive versions 0.54.0 through versions before 0.73.1 should check their deployments.