# CVE-2011-4114: Path traversal in n/a

> Local attackers can overwrite files via predictable temporary directory names in PAR::Packer when another user extracts a packed program.

- **Severity:** Low 3.3 (`AV:L/AC:M/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2012
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-4114, GHSA-gxwf-286g-rc8g, openSUSE-SU-2024:10232-1

## What is CVE-2011-4114?

CVE-2011-4114 is a low-severity path traversal vulnerability in n/a, published on 13 Jan 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The par_mktmpdir function in the PAR::Packer module before 1.012 for Perl creates temporary files in a directory with a predictable name without verifying ownership and permissions of this directory, which allows local users to overwrite files when another user extracts a PAR packed program.  NOTE: a similar vulnerability was reported for PAR, but this has been assigned a different CVE identifier.

Weakness: CWE-264

## Which versions are affected by CVE-2011-4114?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-PAR` | openSUSE:Tumbleweed | All versions | 1.011-1.1 |

Products: Roderich Schupp Par-Packer Module.

## How do I fix CVE-2011-4114?

Upgrade to a fixed version.

## Is CVE-2011-4114 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-5060](https://insights.sbomify.com/CVE-2011-5060/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4114 and fix it if it is affected.

What it is: CVE-2011-4114 is a low-severity path traversal vulnerability in n/a, published on 13 Jan 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-4114 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-2011-4114/ (Markdown: https://insights.sbomify.com/CVE-2011-4114/index.md)
```

## Sources

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

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