How severe is CVE-2013-5671?

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

Which packages are affected by CVE-2013-5671?

CVE-2013-5671 affects the following packages: dragonfly (RubyGems), fog-dragonfly (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-5671?

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

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

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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

Yes. There are 4 known exploit references for CVE-2013-5671, including 4 in-the-wild exploitations 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-5671?

CVE-2013-5671 has an EPSS (Exploit Prediction Scoring System) score of 2.2%, placing it in the 82th 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.

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

CVE-2013-5671 was published on October 24, 2017 and was last updated on December 8, 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

CVE-2013-5671 — dragonfly

Fix: github/advisory-database#486

CVE-2013-5671 is a security vulnerability in dragonfly. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for dragonfly — see the affected versions and patch details below.

Code injection in dragonfly gem

Published

Oct 24, 2017

Updated

Dec 8, 2024

Affected

2 pkgs

Patched

1 / 2

Exploits

4 known

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

EPSS Exploitation Probability

via FIRST.org ↗

2.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

💎dragonfly💎fog-dragonfly

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/dragonfly/imagemagickutils.rb in the fog-dragonfly gem 0.8.2 for Ruby allows remote attackers to execute arbitrary commands via unspecified vectors.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`dragonfly`	all versions	1.0.0`bundle update dragonfly --conservative`
💎RubyGems	`fog-dragonfly`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

fog-dragonflymark_evans

1 version

0.8.2

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/dragonfly/imagemagickutils.rb in the fog-dragonfly gem 0.8.2 for Rub…

seclists.orgNVDMay 2014

Report on seclists.org

seclists.orgNVDMay 2014

Report on vapid.dhs.org

vapid.dhs.orgNVDMay 2014

Report on seclists.org

seclists.orgNVDMay 2014

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dragonfly, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dragonfly to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-5671 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

`lib/dragonfly/imagemagickutils.rb` in the fog-dragonfly gem 0.8.2 for Ruby allows remote attackers to execute arbitrary commands via unspecified vectors.

O3 Security · Impact-Aware SCA

Is CVE-2013-5671 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2013-5671 — dragonfly

EPSS Exploitation Probability

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2013-5671 in your dependencies?