CVE-2014-3211 — publify_core
HIGHCVE-2014-3211 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in publify_core. A fix is available for publify_core — see the affected versions and patch details below.
Publify vulnerable to DoS attack
EPSS Exploitation Probability
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
publify_coreReal-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
Publify before 8.0.1 is vulnerable to a Denial of Service attack
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | publify_core | all versions | 8.0.1bundle update publify_core --conservative |
Affected Products
publifypublifyDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for publify_core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update publify_core to 8.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3211 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2014-3211 in your dependencies?
Find it across RubyGems, including transitive dependencies.