# CVE-2016-20015: Race condition in n/a

> A race condition in the SmokePing init script allows local users to gain root privileges by manipulating file ownership.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2022
- **Updated:** 29 May 2025
- **Also known as:** GHSA-8hvh-7pr8-r6wh, UBUNTU-CVE-2016-20015

## What is CVE-2016-20015?

CVE-2016-20015 is a high-severity vulnerability in n/a, published on 20 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In the ebuild package through smokeping-2.7.3-r1 for SmokePing on Gentoo, the initscript allows the smokeping user to gain ownership of any file, allowing for the smokeping user to gain root privileges. There is a race condition involving /var/lib/smokeping and chown.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2016-20015?

It affects 1 product.


Products: Smokeping Smokeping.

## How do I fix CVE-2016-20015?

No fix has been published for CVE-2016-20015 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-20015 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20015 exists.

## Other vulnerabilities in n/a

- [CVE-2017-20147](https://insights.sbomify.com/CVE-2017-20147/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20015 and fix it if it is affected.

What it is: CVE-2016-20015 is a high-severity vulnerability in n/a, published on 20 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20015 exists.

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

## Sources

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

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