# CVE-2017-16834: Privilege escalation in n/a

> Local attackers can gain root privileges by modifying PNP4Nagios files owned by an unprivileged account, affecting system monitoring infrastructure.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hpg7-623w-gqxj

## What is CVE-2017-16834?

CVE-2017-16834 is a high-severity vulnerability in n/a, published on 16 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PNP4Nagios through 0.6.26 has /usr/bin/npcd and npcd.cfg owned by an unprivileged account but root code execution depends on these files, which allows local users to gain privileges by leveraging access to this unprivileged account.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Pnp4nagios Pnp4nagios.

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

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

## Is CVE-2017-16834 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-38349](https://insights.sbomify.com/CVE-2023-38349/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2023-38350](https://insights.sbomify.com/CVE-2023-38350/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2014-4908](https://insights.sbomify.com/CVE-2014-4908/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2012-3457](https://insights.sbomify.com/CVE-2012-3457/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16834 is a high-severity vulnerability in n/a, published on 16 Nov 2017. 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-2017-16834 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-16834/ (Markdown: https://insights.sbomify.com/CVE-2017-16834/index.md)
```

## Sources

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

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