Attack Chain

1. An attacker crafts a malicious .praison bundle containing a symlink member.
2. The symlink’s name is within the intended destination directory.
3. The symlink’s linkname points to a location outside the destination directory (e.g., /tmp/PWNED).
4. The malicious bundle also includes a regular file member.
5. The regular file’s path traverses through the previously created symlink (e.g., legit/escape/owned.txt).
6. A user or server processes the malicious .praison bundle using praisonai recipe unpack, praisonai recipe pull, or a registry archive validation process.
7. During extraction, the symlink is created first, pointing to the attacker-controlled location.
8. When the regular file is extracted, it follows the symlink, resulting in an arbitrary file write to the attacker’s chosen location.

Impact

Successful exploitation allows an attacker to write arbitrary files with attacker-controlled content to any location on the filesystem accessible to the PraisonAI process. This can lead to various outcomes, including: overwriting user configuration files (.bashrc, .zshrc, .profile, SSH authorized_keys, cron entries), modifying project files, or, if the process runs as root, compromising the entire system. This vulnerability impacts all hosts processing malicious .praison bundles through affected praisonai versions.

Recommendation

• Upgrade to a patched version of PraisonAI that includes the filter="data" argument in the tar.extractall call to prevent symlink extraction bypass (recipe/registry.py:178).
• For older Python versions, implement an explicit check for symlinks and hardlinks during archive extraction, validating that the link target remains within the intended destination directory as described in the suggested remediation.
• Deploy the Sigma rule “Detect PraisonAI Symlink Extraction Bypass” to identify potential exploitation attempts by monitoring for archive extractions containing suspicious symlinks.