tar - Debian Package Tracker

general

source: tar (main)
version: 1.35+dfsg-3.1
maintainer: Janos Lenart (DMD)
uploaders: Carl Worth [DMD]
arch: all any
std-ver: 4.6.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

oldstable: 1.34+dfsg-1+deb11u1
stable: 1.34+dfsg-1.2+deb12u1
testing: 1.35+dfsg-3.1
unstable: 1.35+dfsg-3.1

versioned links

1.34+dfsg-1+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.34+dfsg-1.2+deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.35+dfsg-3.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

tar (89 bugs: 0, 47, 42, 0)
tar-scripts

action needed

1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:

CVE-2025-45582: GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages).

Created: 2025-07-11 Last update: 2025-07-12 06:01

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2025-45582: GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages).

Created: 2025-07-11 Last update: 2025-07-12 06:01

1 security issue in bullseye high

There is 1 open security issue in bullseye.

1 important issue:

CVE-2025-45582: GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages).

Created: 2025-07-11 Last update: 2025-07-12 06:01

1 security issue in bookworm high

There is 1 open security issue in bookworm.

1 important issue:

CVE-2025-45582: GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages).

Created: 2025-07-11 Last update: 2025-07-12 06:01

3 bugs tagged patch in the BTS normal

The BTS contains patches fixing 3 bugs, consider including or untagging them.

Created: 2025-01-06 Last update: 2025-07-21 14:31

lintian reports 3 warnings normal

Lintian reports 3 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2024-12-20 Last update: 2025-04-10 14:02

debian/patches: 7 patches to forward upstream low

Among the 7 debian patches available in version 1.35+dfsg-3.1 of the package, we noticed the following issues:

7 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2024-12-19 16:31

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.2 instead of 4.6.2).

Created: 2024-04-07 Last update: 2025-02-27 13:25

news

[rss feed]

[2024-12-24] tar 1.35+dfsg-3.1 MIGRATED to testing (Debian testing watch)
[2024-12-19] Accepted tar 1.35+dfsg-3.1 (source) into unstable (Reinhard Tartler) (signed by: Gianfranco Costamagna)
[2024-03-09] Accepted tar 1.30+dfsg-6+deb10u1 (source) into oldoldstable (Adrian Bunk)
[2024-01-20] Accepted tar 1.34+dfsg-1+deb11u1 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2024-01-20] Accepted tar 1.34+dfsg-1.2+deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Salvatore Bonaccorso)
[2024-01-17] tar 1.35+dfsg-3 MIGRATED to testing (Debian testing watch)
[2024-01-12] Accepted tar 1.35+dfsg-3 (source) into unstable (Helmut Grohne) (signed by: Gianfranco Costamagna)
[2024-01-03] tar 1.35+dfsg-2 MIGRATED to testing (Debian testing watch)
[2023-12-29] Accepted tar 1.35+dfsg-2 (source) into unstable (Gianfranco Costamagna)
[2023-12-28] Accepted tar 1.35+dfsg-1 (source) into unstable (Gianfranco Costamagna)
[2023-12-25] tar 1.34+dfsg-1.4 MIGRATED to testing (Debian testing watch)
[2023-12-20] Accepted tar 1.34+dfsg-1.4 (source) into unstable (Gianfranco Costamagna)
[2023-12-19] tar 1.34+dfsg-1.3 MIGRATED to testing (Debian testing watch)
[2023-12-13] Accepted tar 1.34+dfsg-1.3 (source) into unstable (Salvatore Bonaccorso)
[2023-04-14] tar 1.34+dfsg-1.2 MIGRATED to testing (Debian testing watch)
[2023-04-08] Accepted tar 1.34+dfsg-1.2 (source) into unstable (Paul Gevers)
[2022-11-20] Accepted tar 1.34+dfsg-1.1 (source) into unstable (Mechtilde Stehmann)
[2021-11-28] Accepted tar 1.29b-1.1+deb9u1 (source) into oldoldstable (Adrian Bunk)
[2021-02-27] tar 1.34+dfsg-1 MIGRATED to testing (Debian testing watch)
[2021-02-17] Accepted tar 1.34+dfsg-1 (source) into unstable (Janos Lenart)
[2021-02-12] Accepted tar 1.33+dfsg-1 (source) into unstable (Janos Lenart)
[2020-12-01] tar 1.32+dfsg-1 MIGRATED to testing (Debian testing watch)
[2020-11-26] Accepted tar 1.32+dfsg-1 (source) into unstable (Janos Lenart)
[2020-03-20] tar 1.30+dfsg-7 MIGRATED to testing (Debian testing watch)
[2020-03-14] Accepted tar 1.30+dfsg-7 (source) into unstable (Bdale Garbee)
[2019-04-29] tar 1.30+dfsg-6 MIGRATED to testing (Debian testing watch)
[2019-04-23] Accepted tar 1.30+dfsg-6 (source amd64) into unstable (Bdale Garbee)
[2019-02-10] tar 1.30+dfsg-5 MIGRATED to testing (Debian testing watch)
[2019-02-04] Accepted tar 1.30+dfsg-5 (source amd64) into unstable (Bdale Garbee)
[2019-01-11] tar 1.30+dfsg-4 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 87 91
RC: 0
I&N: 44 47
M&W: 43 44
F&P: 0
patch: 3

links

homepage
lintian (0, 3)
buildd: logs, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
l10n (-, 85)
debian patches

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1.35+dfsg-3.1
32 bugs (2 patches)