CVE-2014-3211 — Vulnerability in publify_core — CVE Details
Publify vulnerable to DoS attack
Summary
Advisory Timeline
- First published May 17, 2022 (1609 days ago).
- Last revised November 8, 2023 — 539 days after initial publication.
Remediation
Upgrade to the fixed version using your package manager.
gem install publify_core -v 8.0.1
After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.
Affected Packages (1)
Affects 1 ecosystem: rubygems (1).
| Package | Ecosystem | Affected | Fixed In |
|---|---|---|---|
| publify_core | rubygems | All versions | 8.0.1 |
Vulnerability Classification
Common Weakness Enumeration (CWE) identifiers for this vulnerability type.
- CWE-400Uncontrolled Resource ConsumptionMITRE
CVSS Score Breakdown
What the CVSS (Common Vulnerability Scoring System) 7.5 score means for each attack dimension.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
Frequently Asked Questions
- What is CVE-2014-3211?
- Publify vulnerable to DoS attack This vulnerability has been assigned a severity rating of HIGH (CVSS score: 7.5/10).
- How do I check if my project is affected by CVE-2014-3211?
- CVE-2014-3211 affects publify_core. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2014-3211 and 200,000+ other known vulnerabilities.
Severity & Exploitability
High exploitability or significant impact. Prioritize remediation within days.
Also Known As
Related CVEs
- CVE-2022-1811CRITICAL
Publify vulnerable to cross site scripting
- CVE-2023-0299CRITICAL
Publify Improper Input Validation vulnerability
- CVE-2022-1812CRITICAL
Integer overflow in publify_core
- CVE-2022-0524HIGH
Publify Business Logic Errors
- CVE-2022-0574MEDIUM
Publify Incorrect Authorization
- CVE-2022-2815MEDIUM
Publify Core does not strip metadata from images
- CVE-2022-0578MEDIUM
Publify vulnerable to code injection
- CVE-2021-25973MEDIUM
Publify `guest` role users can self-register even when the admin does not allow it
Check if you're affected
Scan your dependencies to see if this vulnerability affects your projects.
Scan Your Dependencies