# CVE-2016-6321: Path traversal in n/a

> Remote attackers can bypass protection mechanisms to write arbitrary files via improper sanitization in GNU tar.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2016
- **Updated:** 6 Aug 2025
- **Also known as:** ALPINE-CVE-2016-6321, DEBIAN-CVE-2016-6321, DLA-690-1, DSA-3702-1, GHSA-4qpm-74c6-fg44, MGASA-2016-0386, SUSE-SU-2016:2895-1, SUSE-SU-2016:2896-1, UBUNTU-CVE-2016-6321, USN-3132-1

## What is CVE-2016-6321?

CVE-2016-6321 is a high-severity path traversal vulnerability in n/a, published on 9 Dec 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2016-6321?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tar` | SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 1.27.1-11.1 |
| `tar` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 1.27.1-11.1 |
| `tar` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 1.26-1.2.10.1 |
| `tar` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 1.27.1-11.1 |
| `tar` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 1.27.1-11.1 |
| `tar` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 1.27.1-11.1 |
| `tar` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 1.26-1.2.10.1 |
| `tar` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.27.1-11.1 |
| `tar` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.27.1-11.1 |

Products: Gnu Tar.

## How do I fix CVE-2016-6321?

Apply the vendor's patch.

## Is CVE-2016-6321 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-6321 exists.

## Other vulnerabilities in n/a

- [CVE-2005-2541](https://insights.sbomify.com/CVE-2005-2541/): Privilege escalation in n/a (critical 10.0)
- [CVE-2019-9923](https://insights.sbomify.com/CVE-2019-9923/): Null dereference in n/a (high 7.5)
- [CVE-2007-4131](https://insights.sbomify.com/CVE-2007-4131/): Path traversal in n/a (medium 6.8)
- [CVE-2023-39804](https://insights.sbomify.com/CVE-2023-39804/): Denial of service in n/a (medium 6.2)
- [CVE-2006-0300](https://insights.sbomify.com/CVE-2006-0300/): Memory corruption in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6321 and fix it if it is affected.

What it is: CVE-2016-6321 is a high-severity path traversal vulnerability in n/a, published on 9 Dec 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-6321 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-6321/ (Markdown: https://insights.sbomify.com/CVE-2016-6321/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-6321
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-6321
- OSV: https://osv.dev/vulnerability/CVE-2016-6321

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-6321/
Summaries are generated and may contain mistakes; the official description above is the record.