# CVE-2017-11746: Race condition in n/a

> Local attackers can exploit a race condition in Tenshi's PID file creation to kill arbitrary processes or escalate privileges via a root script.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-11746, DLA-1069-1, GHSA-m54q-g6pw-5jv7, UBUNTU-CVE-2017-11746

## What is CVE-2017-11746?

CVE-2017-11746 is a high-severity vulnerability in n/a, published on 30 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tenshi 0.15 creates a tenshi.pid file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for tenshi.pid modification before a root script executes a "kill `cat /pathname/tenshi.pid`" command.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2017-11746?

It affects 1 product.


Products: Inversepath Tenshi.

## How do I fix CVE-2017-11746?

Apply the vendor's patch.

## Is CVE-2017-11746 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11746 and fix it if it is affected.

What it is: CVE-2017-11746 is a high-severity vulnerability in n/a, published on 30 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11746 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-2017-11746/ (Markdown: https://insights.sbomify.com/CVE-2017-11746/index.md)
```

## Sources

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

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