How severe is CVE-2013-4479?

No CVSS score has been assigned to CVE-2013-4479 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-4479?

CVE-2013-4479 affects the following packages: sup (RubyGems), sup (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-4479?

Update sup to 0.13.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4479 is resolved across your whole dependency graph.

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

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

How do I mitigate CVE-2013-4479 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-4479 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2013-4479, 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-4479?

CVE-2013-4479 has an EPSS (Exploit Prediction Scoring System) score of 3.2%, placing it in the 88th 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-4479?

CVE-2013-4479 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2013-4479 was published on December 7, 2013 and was last updated on April 10, 2026. 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

CVE-2013-4479 — sup

Fix: sup-heliotrope/sup@ca0302e

CVE-2013-4479 is a Code Injection vulnerability in sup. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for sup — see the affected versions and patch details below.

Sup Code Injection vulnerability

Also known asGHSA-hh2x-7mf9-78fr

Published

Dec 7, 2013

Updated

Apr 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

3.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

💎sup💎sup

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

lib/sup/message_chunks.rb in Sup before 0.13.2.1 and 0.14.x before 0.14.1.1 allows remote attackers to execute arbitrary commands via shell metacharacters in the content_type of an email attachment.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`sup`	all versions	0.13.2.1`bundle update sup --conservative`
💎RubyGems	`sup`	≥ 0.14.0&&< 0.14.1.1	0.14.1.1`bundle update sup --conservative`

Affected Products

1 product · 5 configurations

Application

supsupmua

≤ 0.13.2

4 versions

0.13.00.13.10.14.00.14.1

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.

lib/sup/message_chunks.rb in Sup before 0.13.2.1 and 0.14.x before 0.14.…

github.comNVDDec 2016

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sup, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update sup to 0.13.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4479 is resolved across your whole dependency graph.
Workarounds
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

lib/sup/message_chunks.rb in Sup before 0.13.2.1 and 0.14.x before 0.14.1.1 allows remote attackers to execute arbitrary commands via shell metacharacters in the content_type of an email attachment.

O3 Security · Impact-Aware SCA

Is CVE-2013-4479 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works