How severe is CVE-2013-2095?

CVE-2013-2095 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2013-2095?

CVE-2013-2095 affects the following packages: openshift-origin-controller (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-2095?

The records we use list no patched version of openshift-origin-controller for CVE-2013-2095. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2013-2095 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openshift-origin-controller, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-2095 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2013-2095 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2013-2095, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-2095?

CVE-2013-2095 has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-2095?

CVE-2013-2095 is classified as CWE-74 (CWE-74). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2013-2095 published, and has it been updated?

CVE-2013-2095 was published on May 5, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎

💎 RubyGems

Not in CISA KEV

CRITICAL severity

CVE-2013-2095 — openshift-origin-controll…

CRITICAL

CVE-2013-2095 is a critical-severity (CVSS 9.8) CWE-74 vulnerability in openshift-origin-controller. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

RubyGem openshift-origin-controller is vulnerable to command injection

Published

May 5, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

See advisory

Exploits

1 known

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

💎openshift-origin-controller

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

rubygem-openshift-origin-controller: API can be used to create applications via cartridge_cache.rb URI.prase() to perform command injection

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`openshift-origin-controller`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

openshift-origin-controlleropenshift-origin-controller_project

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

rubygem-openshift-origin-controller: API can be used to create applicati…

bugzilla.redhat.comNVDDec 2019

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openshift-origin-controller, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of openshift-origin-controller for CVE-2013-2095. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

rubygem-openshift-origin-controller: API can be used to create applications via cartridge_cache.rb URI.prase() to perform command injection

O3 Security · Impact-Aware SCA

Is CVE-2013-2095 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-74CWE-74

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

First exploit

Dec 17, 2019

Disclosed

May 5, 2022

Last updated

Feb 16, 2024

Identifiers

CVE-2013-2095

References

Advisorynvd.nist.gov · CVE 2013 2095 Webaccess.redhat.com · cve 2013 2095 Webbugzilla.redhat.com · show bug.cgi Webgithub.com · CVE 2013 2095.yml Packagegithub.com · origin server

Related vulnerabilities

This CVE is critical severity; 1 of 8 other CVEs with CWE-74 is rated as high or higher (top: critical).

CVE-2026-96634CVE-2026-118258CVE-2026-115730CVE-2026-105800CVE-2026-101900CVE-2026-101904CVE-2026-61732GHSA-wwv5-g3v4-889xBrowse all CWE-74

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

CVE-2013-2095 — openshift-origin-controll…

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2013-2095 in your dependencies?