Skip to content
Noroxi
CVE-2016-6321· NVD / CVE Program· CNA redhat

Directory traversal vulnerability in the safer_name_suffix function in GNU tar 1.14 through 1.29 might allow remote attackers to bypass an i

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Dec 9, 2016
Updated
Jun 16, 2026
EPSS
15.7% · 97th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
5 / 30 · 15.7%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Affected systems

VendorProduct
gnutar

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gnu tar1.14
  • gnu tar1.15
  • gnu tar1.15.1
  • gnu tar1.15.90
  • gnu tar1.15.91
  • gnu tar1.16
  • gnu tar1.16.1
  • gnu tar1.17
  • gnu tar1.18
  • gnu tar1.19
  • gnu tar1.20
  • gnu tar1.21
  • gnu tar1.22
  • gnu tar1.23
  • gnu tar1.24
  • gnu tar1.25
  • gnu tar1.26
  • gnu tar1.27
  • gnu tar1.27.1
  • gnu tar1.28

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10tarbefore 1.29-r11.29-r1
Debian:12tarbefore 1.29b-1.11.29b-1.1
Debian:7tarbefore 1.26+dfsg-0.1+deb7u11.26+dfsg-0.1+deb7u1
Debian:8tarbefore 1.27.1-2+deb8u11.27.1-2+deb8u1
openSUSE:Tumbleweedtarbefore 1.29-2.11.29-2.1
SUSE:Linux Enterprise Desktop 12 SP1tarbefore 1.27.1-11.11.27.1-11.1
SUSE:Linux Enterprise Server 11 SP4tarbefore 1.26-1.2.10.11.26-1.2.10.1

Same product

gnu: all records

Other highest-scoring records for the same primary product.

  • CVE-2005-2541Tar 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 p
    41Plan
  • CVE-2007-4476Buffer overflow in the safer_name_suffix function in GNU tar has unspecified attack vectors and impact, resulting in a "crashing stack."
    34Monitor
  • CVE-2019-9923pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that have malformed extend
    31Monitor
  • CVE-2007-4131Directory traversal vulnerability in the contains_dot_dot function in src/names.c in GNU tar allows user-assisted remote attackers to overwr
    28Monitor
  • CVE-2023-39804In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.
    24Monitor
  • CVE-2026-5704Tar: tar: hidden file injection via crafted archives
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:tar1.29-r1 · Alpine:v3.10Package registry (OSV)
debian:tar1.29b-1.1 · Debian:12Package registry (OSV)
opensuse:tar1.29-2.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:tar1.26-1.2.10.1 · SUSE:Linux Enterprise Server 11 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records