# CVE-2007-4131: Path traversal in n/a

> Attackers can overwrite arbitrary files via crafted TAR archives with directory traversal sequences, requiring user interaction to extract the archive.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-4131, GHSA-43w6-q9mv-9cwf, RHSA-2007:0860

## What is CVE-2007-4131?

CVE-2007-4131 is a medium-severity path traversal vulnerability in n/a, published on 25 Aug 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Directory traversal vulnerability in the contains_dot_dot function in src/names.c in GNU tar allows user-assisted remote attackers to overwrite arbitrary files via certain //.. (slash slash dot dot) sequences in directory symlinks in a TAR archive.

## Which versions are affected by CVE-2007-4131?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tar` | Red Hat:enterprise_linux:4::as | All versions | 0:1.14-12.5.1.RHEL4 |
| `tar-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:1.14-12.5.1.RHEL4 |
| `tar` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.14-12.5.1.RHEL4 |
| `tar-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:1.14-12.5.1.RHEL4 |
| `tar` | Red Hat:enterprise_linux:4::es | All versions | 0:1.14-12.5.1.RHEL4 |
| `tar-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:1.14-12.5.1.RHEL4 |
| `tar` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.14-12.5.1.RHEL4 |
| `tar-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:1.14-12.5.1.RHEL4 |
| `tar` | Red Hat:enterprise_linux:5::client | All versions | 2:1.15.1-23.0.1.el5 |
| `tar-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 2:1.15.1-23.0.1.el5 |
| `tar` | Red Hat:enterprise_linux:5::server | All versions | 2:1.15.1-23.0.1.el5 |
| `tar-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 2:1.15.1-23.0.1.el5 |

Products: Gnu Tar.

## How do I fix CVE-2007-4131?

Upgrade to a fixed version.

## Is CVE-2007-4131 being exploited?

There is no known exploitation of CVE-2007-4131 in the wild and no public exploit code.

## 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-2016-6321](https://insights.sbomify.com/CVE-2016-6321/): Path traversal in n/a (high 7.5)
- [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-2007-4131 and fix it if it is affected.

What it is: CVE-2007-4131 is a medium-severity path traversal vulnerability in n/a, published on 25 Aug 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-4131 in the wild and no public exploit code.

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-2007-4131/ (Markdown: https://insights.sbomify.com/CVE-2007-4131/index.md)
```

## Sources

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

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