# CVE-2014-0068: Misconfiguration in openshift node-util

> Insecure file permissions on watchman logs and PID files allow local attackers to modify or corrupt these files, potentially leading to privilege escalation.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 30 Jun 2022
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3w8r-2x8f-g5jx

## What is CVE-2014-0068?

CVE-2014-0068 is a medium-severity vulnerability in openshift node-util, published on 30 Jun 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

It was reported that watchman in openshift node-utils creates /var/run/watchman.pid and /var/log/watchman.ouput with world writable permission.

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

## Which versions are affected by CVE-2014-0068?

It affects 1 product.


Products: Redhat Openshift-Origin-Node-Util.

## How do I fix CVE-2014-0068?

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

## Is CVE-2014-0068 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0068 and fix it if it is affected.

What it is: CVE-2014-0068 is a medium-severity vulnerability in openshift node-util, published on 30 Jun 2022. 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-2014-0068 in the wild and no public exploit code.

Affected product: openshift node-util. 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-2014-0068/ (Markdown: https://insights.sbomify.com/CVE-2014-0068/index.md)
```

## Sources

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

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