The vulnerability in zarf (versions 0.23.0 to 0.74.1) arises from improper limitation of a pathname to a restricted directory (CWE-22). The 'zarf package inspect sbom' and 'zarf package inspect documentation' subcommands create output file paths by concatenating a user-supplied output directory with the Metadata.Name field from the package's zarf.yaml manifest. Although Metadata.Name is initially validated against a regex during package creation, an attacker can modify this field after unarchiving the package to include path traversal sequences (e.g., '../../etc/cron.d/malicious') or absolute paths (e.g., '/home/user/.ssh/authorized_keys'). This manipulation enables arbitrary file writes with the permissions of the user running the inspect command. The issue was addressed and fixed in zarf version 0.74.2.

An attacker who can supply or modify a zarf package can exploit this vulnerability to write arbitrary files to arbitrary locations on the filesystem where the inspect command is run. This can lead to unauthorized file modification or creation, potentially enabling further compromise depending on the files overwritten. The impact is limited to the permissions of the user executing the command. There are no known exploits in the wild as of the published date.

This vulnerability is fixed in zarf version 0.74.2. Users should upgrade to version 0.74.2 or later to remediate this issue. Patch status is not explicitly stated in the vendor advisory, but the fix is included in the specified version. Until upgrading, avoid running the vulnerable subcommands on untrusted packages or in environments where arbitrary file writes could cause harm.