tar is vulnerable to PAX Header Desynchronization
53
Medium Risk
When a tar stream places a PAX extended header before intermediary extension records such as a GNU longname block, the crate applies pending PAX metadata to those extension headers instead of the next file entry. This desynchronizes parsing relative to POSIX pax and other tar implementations, so a crafted archive can list or extract different members depending on the parser. An attacker can use that differential to smuggle or hide files during extraction. The fix skips applying PAX overrides to extension header types and associates them only with the following file entry.
You are affected if you are using a version that falls within the vulnerable range.
tar is vulnerable to PAX Header Desynchronization in versions 0.0.1 - 0.4.45.
Upgrade the tar library to version 0.4.46.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

SOC 2Compliant
ISO 27001Compliant