OpenshiftApplication · Redhat
CVE-2014-0023
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenShift: Install script has temporary file creation vulnerability which can result in arbitrary code execution
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpenShift contains a temporary file creation vulnerability in its install script where insecure handling of temporary files can be exploited to achieve arbitrary code execution. The vulnerability stems from the install script creating temporary files in a predictable manner without proper safeguards, allowing an attacker to potentially overwrite or inject malicious content during the file creation window.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
OpenshiftApplication
all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm OpenShift installationRun 'oo-version' or check for OpenShift packages via package manager (e.g., 'rpm -qa | grep openshift')Affected if OpenShift is installed on the system
-
Locate OpenShift install scriptsSearch for install/setup scripts in common locations such as /usr/local/bin, /opt, /usr/share/openshift, or the directory where OpenShift was originally installedAffected if Install scripts exist and contain temporary file creation logic
-
Inspect scripts for insecure temp file creationExamine install scripts for patterns like direct file redirection to /tmp (e.g., '> /tmp/filename'), hardcoded temp filenames without random tokens, or missing use of mktemp/mkstemp commandsAffected if Scripts create temporary files without using secure methods like mktemp or mkstemp, or use predictable filenames
-
Check file permissions on temp file operationsReview scripts to verify whether proper file permissions (e.g., mode 0600) are set when creating temporary filesAffected if Temporary files are created without secure permissions or in world-writable directories like /tmp
A system is affected if it runs OpenShift with install scripts that use insecure, predictable temporary file creation methods instead of secure alternatives like mktemp.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace insecure temporary file creation in the install script with secure methods such as mktemp or mkstemp, ensuring proper file permissions and avoiding predictable file paths. Apply any available OpenShift patches or updates to the install scripts.
Fix this in Openshift
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0023 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0023 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data