dbcve.org
OpenshiftApplication · Redhat

CVE-2014-3496

HIGH · 10.0 CVSS v2.0 Published 2014-06-20
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
cartridge_repository.rb in OpenShift Origin and Enterprise 1.2.8 through 2.1.1 allows remote attackers to execute arbitrary commands via shell metacharacters in a Source-Url ending with a (1) .tar.gz, (2) .zip, (3) .tgz, or (4) .tar file extension in a cartridge manifest file.

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 · high confidence

The cartridge_repository.rb component in OpenShift Origin and Enterprise versions 1.2.8 through 2.1.1 fails to sanitize shell metacharacters from the Source-Url field in cartridge manifest files. When processing URLs ending in .tar.gz, .zip, .tgz, or .tar extensions, the unsanitized input is passed to a shell execution context, allowing remote attackers to inject and execute arbitrary commands.

MitigationUpgrade OpenShift Origin/Enterprise to a version beyond 2.1.1 that contains the patched cartridge_repository.rb, or implement strict input validation to reject shell metacharacters in the Source-Url field before shell execution.

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
Affected:= 1.2.8= 2.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.1= 2.1.1
Openshift OriginApplication
Affected:= 1.2.8= 2.1= 2.1.1

CVSS 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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenShift Origin or Enterprise version
    Run 'oo-version' or check /etc/openshift/origin_version file to determine the installed version of OpenShift Origin or Enterprise
    Affected if The installed version is 1.2.8, 2.0 through 2.0.6, or 2.1 through 2.1.1 for either product
  2. Locate cartridge_repository.rb component
    Search for the file cartridge_repository.rb in the OpenShift installation directory, typically under /usr/lib/openshift/broker/lib or similar paths within the broker codebase
    Affected if The file exists and contains shell execution code that processes the Source-Url field from cartridge manifests
  3. Verify vulnerable URL processing pattern
    Examine cartridge_repository.rb for code that passes the Source-Url parameter directly to system(), exec(), or backtick shell execution without sanitization, especially within methods handling .tar.gz, .zip, .tgz, or .tar URL extensions
    Affected if Code directly interpolates the Source-Url into a shell command without escaping shell metacharacters
  4. Check for cartridge manifest usage
    Review the OpenShift broker configuration and gear types to determine if custom cartridges are being installed, which would trigger processing of cartridge manifest files with Source-Url fields
    Affected if Custom cartridge manifests with Source-Url fields ending in .tar.gz, .zip, .tgz, or .tar are being processed by the broker
  5. Audit recent cartridge download activity
    Review broker logs for downloads of cartridge packages with .tar.gz, .zip, .tgz, or .tar extensions from the Source-Url field to identify potential exploitation attempts
    Affected if Logs show cartridge downloads where the Source-Url was processed through shell execution

You are affected if you run OpenShift Origin or Enterprise versions 1.2.8 through 2.1.1 and your broker processes cartridge manifest files with Source-Url fields containing URLs with shell metacharacters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade OpenShift Origin/Enterprise to a version beyond 2.1.1 that contains the patched cartridge_repository.rb, or implement strict input validation to reject shell metacharacters in the Source-Url field before shell execution.

Recommended fix Moderate confidence

OpenShift Origin 2.1.2 or later

  1. Identify the current OpenShift Origin or Enterprise version deployed
  2. If version is 1.2.8 through 2.1.1, plan for upgrade or patch
  3. Review the security fix in GitHub pull request #5521 at https://github.com/openshift/origin-server/pull/5521
  4. Apply the patch from the PR or upgrade to a version newer than 2.1.1
  5. Verify the fix by testing cartridge manifest file processing with malicious Source-Url payloads

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openshift Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA6.0 h
26.0 hours of engineering $4,520
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,232.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3496 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-3496 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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