Tar GNU Tar

Do you want an email whenever new security vulnerabilities are reported in GNU Tar?

By the Year

In 2023 there have been 1 vulnerability in GNU Tar with an average score of 7.8 out of ten. Tar did not have any published security vulnerabilities last year. That is, 1 more vulnerability have already been reported in 2023 as compared to last year.

Year Vulnerabilities Average Score
2023 1 7.80
2022 0 0.00
2021 1 5.50
2020 0 0.00
2019 1 7.50
2018 1 4.70

It may take a day or so for new Tar vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent GNU Tar Security Vulnerabilities

GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump

CVE-2022-48303 7.8 - High - January 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 approximately 11 whitespace characters.

Out-of-bounds Read

A flaw was found in the src/list.c of tar 1.33 and earlier

CVE-2021-20193 5.5 - Medium - March 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.

Out-of-bounds Read

pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives

CVE-2019-9923 7.5 - High - March 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.

NULL Pointer Dereference

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

CVE-2018-20482 4.7 - Medium - December 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 process (e.g., a system backup running as root).

Infinite Loop

Directory traversal vulnerability in the safer_name_suffix function in GNU tar 1.14 through 1.29 might

CVE-2016-6321 7.5 - High - December 09, 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 POINTYFEATHER.

Directory traversal

Buffer overflow in the safer_name_suffix function in GNU tar has unspecified attack vectors and impact, resulting in a "crashing stack

CVE-2007-4476 - September 05, 2007

Buffer overflow in the safer_name_suffix function in GNU tar has unspecified attack vectors and impact, resulting in a "crashing stack."

Buffer Overflow

Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may

CVE-2005-2541 - August 10, 2005

Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for GNU Tar or by GNU? Click the Watch button to subscribe.

GNU
Vendor

GNU Tar
Product

subscribe