OpenshiftApplication · Redhat
CVE-2014-0163
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 has shell command injection flaws due to unsanitized data being passed into shell commands.
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 shell command injection vulnerabilities where unsanitized user input is passed directly to shell commands, allowing remote attackers to execute arbitrary operating system commands on the underlying hosts.
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
= 1.0= 2.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify OpenShift versionRun 'oo-version' or check /etc/openshift/origin-servers.json or rpm -qa | grep openshift to determine the installed OpenShift versionAffected if Version is 1.0 or 2.0 (exact match)
-
Locate user-facing applicationsList all gears and applications using 'rhc apps' or 'oc get projects' and identify which accept external user input via web forms, APIs, or command-line argumentsAffected if Applications that accept user input are deployed on affected OpenShift versions
-
Inspect custom cartridges or hooksExamine .openshift/action_hooks directories and custom cartridge scripts in /usr/libexec/openshift/cartridges/ for direct shell command execution using system(), exec(), or shell interpolation of user-supplied variablesAffected if Cartridge or hook scripts pass unsanitized environment variables or user parameters directly to shell commands
-
Review environment variable handlingSearch gear environment variables and application code for use of ENV vars like $OPENSHIFT_* in shell commands without escaping or validation, particularly in action hooks and cron scriptsAffected if Application code or cartridge hooks execute shell commands using user-influenced environment variables without sanitization
Environment is affected if OpenShift version is exactly 1.0 or 2.0 AND user-supplied input can reach shell execution functions without validation in any deployed application or cartridge.
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 dataImplement strict input validation and sanitization for all user-supplied data, and avoid passing untrusted input directly to shell execution functions by using parameterized APIs or escaping functions where shell use is unavoidable.
Fix this in Openshift
Scoped from the published advisory
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0163 — 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-0163 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