Local file tampering via world-writable Watchman files
Published Jun 30, 2022 · Updated Aug 6, 2024
Incorrect file permissions in Red Hat openshift-origin-node-util for OpenShift 1.x and 2.x allow local users to modify Watchman files. Watchman creates /var/run/watchman.pid and /var/log/watchman.ouput with permissions that permit any local user to write them. Local account access is required; modification can corrupt PID or log data, but public records do not establish code execution.
Summary
What happened
Incorrect file permissions in Red Hat openshift-origin-node-util for OpenShift 1.x and 2.x allow local users to modify Watchman files. Watchman creates /var/run/watchman.pid and /var/log/watchman.ouput with permissions that permit any local user to write them. Local account access is required; modification can corrupt PID or log data, but public records do not establish code execution.
The record
- CVE
- CVE-2014-0068
- Published
- Jun 30, 2022
- Updated
- Aug 6, 2024
- Vendor
- Red Hat
- Product
- openshift-origin-node-util
- Classifications
- CWE-732
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2022CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=openshift node-util as shipped in Openshift Enterprise 1.x and 2.x
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo