# CVE-2015-0267: Path traversal in n/a

> Local attackers can write to arbitrary files via a symlink attack in the kexec-tools setup script, potentially compromising system integrity.

- **Severity:** Low 3.6 (`AV:L/AC:L/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:** 19 May 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v9pv-3899-728j, RHSA-2015:0986

## What is CVE-2015-0267?

CVE-2015-0267 is a low-severity path traversal vulnerability in n/a, published on 19 May 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Red Hat module-setup.sh script for kexec-tools, as distributed in the kexec-tools before 2.0.7-19 packages in Red Hat Enterprise Linux, allows local users to write to arbitrary files via a symlink attack on a temporary file.

## Which versions are affected by CVE-2015-0267?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kexec-tools` | Red Hat:enterprise_linux:7::client | All versions | 0:2.0.7-19.el7_1.2 |
| `kexec-tools-anaconda-addon` | Red Hat:enterprise_linux:7::client | All versions | 0:2.0.7-19.el7_1.2 |
| `kexec-tools-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:2.0.7-19.el7_1.2 |
| `kexec-tools-eppic` | Red Hat:enterprise_linux:7::client | All versions | 0:2.0.7-19.el7_1.2 |
| `kexec-tools` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.0.7-19.el7_1.2 |
| `kexec-tools-anaconda-addon` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.0.7-19.el7_1.2 |
| `kexec-tools-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.0.7-19.el7_1.2 |
| `kexec-tools-eppic` | Red Hat:enterprise_linux:7::computenode | All versions | 0:2.0.7-19.el7_1.2 |
| `kexec-tools` | Red Hat:enterprise_linux:7::server | All versions | 0:2.0.7-19.ael7b_1.2 |
| `kexec-tools-anaconda-addon` | Red Hat:enterprise_linux:7::server | All versions | 0:2.0.7-19.ael7b_1.2 |
| `kexec-tools-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:2.0.7-19.ael7b_1.2 |
| `kexec-tools-eppic` | Red Hat:enterprise_linux:7::server | All versions | 0:2.0.7-19.ael7b_1.2 |
| `kexec-tools` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.0.7-19.el7_1.2 |
| `kexec-tools-anaconda-addon` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.0.7-19.el7_1.2 |
| `kexec-tools-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.0.7-19.el7_1.2 |
| `kexec-tools-eppic` | Red Hat:enterprise_linux:7::workstation | All versions | 0:2.0.7-19.el7_1.2 |

Products: Redhat Kexec-Tools.

## How do I fix CVE-2015-0267?

Apply the vendor's patch.

## Is CVE-2015-0267 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3588](https://insights.sbomify.com/CVE-2011-3588/): Security feature bypass in n/a (medium 5.7)
- [CVE-2011-3589](https://insights.sbomify.com/CVE-2011-3589/): Information disclosure in n/a (medium 5.7)
- [CVE-2011-3590](https://insights.sbomify.com/CVE-2011-3590/): Information disclosure in n/a (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0267 and fix it if it is affected.

What it is: CVE-2015-0267 is a low-severity path traversal vulnerability in n/a, published on 19 May 2015. 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-2015-0267 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-2015-0267/ (Markdown: https://insights.sbomify.com/CVE-2015-0267/index.md)
```

## Sources

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

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