Skip to content
Fencer Intel
medium 6.5

CVE-2014-0233 json

Red Hat OpenShift Enterprise 2.0 and 2.1 and OpenShift Origin allow remote authenticated users to execute arbitrary commands via shell meta…

published 2014-11-16 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-0271

cvss
6.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

Red Hat OpenShift Enterprise 2.0 and 2.1 and OpenShift Origin allow remote authenticated users to execute arbitrary commands via shell metacharacters in a directory name that is referenced by a cartridge using the file: URI scheme.

Patch / fix

  • rubygem-openshift-origin-node openshift 2.0 1.23.9.4-1.el6op
  • rubygem-openshift-origin-node openshift 2.0 1.17.5.16-1.el6op

red hat advisories RHSA-2014:0530RHSA-2014:0529

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-0233 updated cvss 7.2

OpenShift: downloadable cartridge source url file command execution as root

  • Red Hat OpenShift Enterprise 1 rubygem-openshift-origin-node
    affected: no fix available
  • Red Hat RHOSE Node 2.0 rubygem-openshift-origin-node 1.17.5.16-1.el6op
    fixed: vendor fix RHSA-2014:0529
  • Red Hat RHOSE Node 2.1 rubygem-openshift-origin-node 1.23.9.4-1.el6op
    fixed: vendor fix RHSA-2014:0530

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.72% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=1096955 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.