rpm package
opensuse/tar&distro=openSUSE Tumbleweed
pkg:rpm/opensuse/tar&distro=openSUSE%20Tumbleweed
Vulnerabilities (13)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2025-45582 | — | < 1.35-7.1 | 1.35-7.1 | Jul 11, 2025 | 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 c | ||
| CVE-2023-39804 | — | < 1.35-2.1 | 1.35-2.1 | Mar 27, 2024 | In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c. | ||
| CVE-2022-48303 | — | < 1.34-10.1 | 1.34-10.1 | Jan 30, 2023 | GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approxima | ||
| CVE-2021-20193 | — | < 1.34-5.1 | 1.34-5.1 | Mar 26, 2021 | A flaw was found in the src/list.c of tar 1.33 and earlier. This flaw allows an attacker who can submit a crafted input file to tar to cause uncontrolled consumption of memory. The highest threat from this vulnerability is to system availability. | ||
| CVE-2019-9923 | — | < 1.34-2.2 | 1.34-2.2 | Mar 22, 2019 | pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that have malformed extended headers. | ||
| CVE-2018-20482 | — | < 1.34-2.2 | 1.34-2.2 | Dec 26, 2018 | GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which allows local users to cause a denial of service (infinite read loop in sparse_dump_region in sparse.c) by modifying a file that is supposed to be archived by a different user's proces | ||
| CVE-2016-6321 | Hig | 7.5 | < 1.29-2.1 | 1.29-2.1 | Dec 9, 2016 | Directory traversal vulnerability in the safer_name_suffix function in GNU tar 1.14 through 1.29 might allow remote attackers to bypass an intended protection mechanism and write to arbitrary files via vectors related to improper sanitization of the file_name parameter, aka POINT | |
| CVE-2010-0624 | — | < 1.29-2.1 | 1.29-2.1 | Mar 15, 2010 | Heap-based buffer overflow in the rmt_read__ function in lib/rtapelib.c in the rmt client functionality in GNU tar before 1.23 and GNU cpio before 2.11 allows remote rmt servers to cause a denial of service (memory corruption) or possibly execute arbitrary code by sending more da | ||
| CVE-2006-6097 | — | < 1.34-2.2 | 1.34-2.2 | Nov 24, 2006 | GNU tar 1.16 and 1.15.1, and possibly other versions, allows user-assisted attackers to overwrite arbitrary files via a tar file that contains a GNUTYPE_NAMES record with a symbolic link, which is not properly handled by the extract_archive function in extract.c and extract_mangl | ||
| CVE-2006-0300 | — | < 1.34-2.2 | 1.34-2.2 | Feb 24, 2006 | Buffer overflow in tar 1.14 through 1.15.90 allows user-assisted attackers to cause a denial of service (application crash) and possibly execute code via unspecified vectors involving PAX extended headers. | ||
| CVE-2005-1918 | — | < 1.34-2.2 | 1.34-2.2 | Dec 31, 2005 | The original patch for a GNU tar directory traversal vulnerability (CVE-2002-0399) in Red Hat Enterprise Linux 3 and 2.1 uses an "incorrect optimization" that allows user-assisted attackers to overwrite arbitrary files via a crafted tar file, probably involving "/../" sequences w | ||
| CVE-2002-0399 | — | < 1.34-2.2 | 1.34-2.2 | Oct 10, 2002 | Directory traversal vulnerability in GNU tar 1.13.19 through 1.13.25, and possibly later versions, allows attackers to overwrite arbitrary files during archive extraction via a (1) "/.." or (2) "./.." string, which removes the leading slash but leaves the "..", a variant of CVE-2 | ||
| CVE-2001-1267 | — | < 1.34-2.2 | 1.34-2.2 | Jul 12, 2001 | Directory traversal vulnerability in GNU tar 1.13.19 and earlier allows local users to overwrite arbitrary files during archive extraction via a tar file whose filenames contain a .. (dot dot). |
- CVE-2025-45582Jul 11, 2025affected < 1.35-7.1fixed 1.35-7.1
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 c
- CVE-2023-39804Mar 27, 2024affected < 1.35-2.1fixed 1.35-2.1
In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.
- CVE-2022-48303Jan 30, 2023affected < 1.34-10.1fixed 1.34-10.1
GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approxima
- CVE-2021-20193Mar 26, 2021affected < 1.34-5.1fixed 1.34-5.1
A flaw was found in the src/list.c of tar 1.33 and earlier. This flaw allows an attacker who can submit a crafted input file to tar to cause uncontrolled consumption of memory. The highest threat from this vulnerability is to system availability.
- CVE-2019-9923Mar 22, 2019affected < 1.34-2.2fixed 1.34-2.2
pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that have malformed extended headers.
- CVE-2018-20482Dec 26, 2018affected < 1.34-2.2fixed 1.34-2.2
GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which allows local users to cause a denial of service (infinite read loop in sparse_dump_region in sparse.c) by modifying a file that is supposed to be archived by a different user's proces
- affected < 1.29-2.1fixed 1.29-2.1
Directory traversal vulnerability in the safer_name_suffix function in GNU tar 1.14 through 1.29 might allow remote attackers to bypass an intended protection mechanism and write to arbitrary files via vectors related to improper sanitization of the file_name parameter, aka POINT
- CVE-2010-0624Mar 15, 2010affected < 1.29-2.1fixed 1.29-2.1
Heap-based buffer overflow in the rmt_read__ function in lib/rtapelib.c in the rmt client functionality in GNU tar before 1.23 and GNU cpio before 2.11 allows remote rmt servers to cause a denial of service (memory corruption) or possibly execute arbitrary code by sending more da
- CVE-2006-6097Nov 24, 2006affected < 1.34-2.2fixed 1.34-2.2
GNU tar 1.16 and 1.15.1, and possibly other versions, allows user-assisted attackers to overwrite arbitrary files via a tar file that contains a GNUTYPE_NAMES record with a symbolic link, which is not properly handled by the extract_archive function in extract.c and extract_mangl
- CVE-2006-0300Feb 24, 2006affected < 1.34-2.2fixed 1.34-2.2
Buffer overflow in tar 1.14 through 1.15.90 allows user-assisted attackers to cause a denial of service (application crash) and possibly execute code via unspecified vectors involving PAX extended headers.
- CVE-2005-1918Dec 31, 2005affected < 1.34-2.2fixed 1.34-2.2
The original patch for a GNU tar directory traversal vulnerability (CVE-2002-0399) in Red Hat Enterprise Linux 3 and 2.1 uses an "incorrect optimization" that allows user-assisted attackers to overwrite arbitrary files via a crafted tar file, probably involving "/../" sequences w
- CVE-2002-0399Oct 10, 2002affected < 1.34-2.2fixed 1.34-2.2
Directory traversal vulnerability in GNU tar 1.13.19 through 1.13.25, and possibly later versions, allows attackers to overwrite arbitrary files during archive extraction via a (1) "/.." or (2) "./.." string, which removes the leading slash but leaves the "..", a variant of CVE-2
- CVE-2001-1267Jul 12, 2001affected < 1.34-2.2fixed 1.34-2.2
Directory traversal vulnerability in GNU tar 1.13.19 and earlier allows local users to overwrite arbitrary files during archive extraction via a tar file whose filenames contain a .. (dot dot).