# CVE-2013-4159: Other in n/a

> Insecure temporary file creation in CTDB allows local attackers to potentially escalate privileges or modify data via race conditions.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/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:** 6 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4pj4-x8fv-v6vm, MGASA-2014-0274

## What is CVE-2013-4159?

CVE-2013-4159 is a high-severity vulnerability in Opensuse Opensuse, published on 6 Aug 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ctdb before 2.3 in OpenSUSE 12.3 and 13.1 does not create temporary files securely, which has unspecified impact related to "several temp file vulnerabilities" in (1) tcp/tcp_connect.c, (2) server/eventscript.c, (3) tools/ctdb_diagnostics, (4) config/gdb_backtrace, and (5) include/ctdb_private.h.

Weakness: CWE-264

## Which versions are affected by CVE-2013-4159?

It affects 3 products.


Products: Ctdb Project Ctdb, Mageia Mageia, Opensuse Opensuse.

## How do I fix CVE-2013-4159?

Upgrade to a fixed version.

## Is CVE-2013-4159 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4159 and fix it if it is affected.

What it is: CVE-2013-4159 is a high-severity vulnerability in Opensuse Opensuse, published on 6 Aug 2014. 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-2013-4159 in the wild and no public exploit code.

Affected product: Opensuse Opensuse. 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-2013-4159/ (Markdown: https://insights.sbomify.com/CVE-2013-4159/index.md)
```

## Sources

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

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