Skip to content

Product

ubuntu/tar vulnerabilities

10 published CVES affecting ubuntu/tar, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
10
Critical
0
High
2
Medium
7
Low
1
Unscored
0
CISA KEV
0

Latest ubuntu/tar CVEs

Newest publication first

  1. MediumCVSS 5.5 EPSS 0.47%

    A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce...

  2. MediumCVSS 4.1 EPSS 0.49%

    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...

  3. MediumCVSS 5.5 EPSS 1.5%

    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...

  4. LowCVSS 3.3 EPSS 1.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.

  5. MediumCVSS 4.7 EPSS 0.53%

    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...

  6. HighCVSS 7.5 EPSS 15.7%

    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...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.