GHSA-vq74-9583-hrm4 CVE-2014-3211
Publify vulnerable to DoS attack
High
RubyGems
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 1.08%
- Chance of exploitation in the next 30 days. Higher than 65.20% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
8.0.1- Upgrade publify_core to this version or later
Description
Publify before 8.0.1 is vulnerable to a Denial of Service attack
Affected versions
RubyGems
| Package | Vulnerable | Fixed in |
|---|---|---|
| publify_core | < 8.0.1 |
8.0.1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
publify_core RubyGems → 8.0.1
- bundler
bundle update publify_core # Gemfile: gem "publify_core", ">= 8.0.1"
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-8fm5-gg2f-f66q Publify Vulnerable To Cross-Site Scripting (XSS) Via Redirects Requiring User Interaction | Medium | Also affects publify_core |
| GHSA-g7gf-2rqw-5rwx Publify contains Weak Password Requirements | Medium | Also affects publify_core |
| GHSA-rc42-jghf-vr8f Integer overflow in publify_core | Critical | Also affects publify_core |
| GHSA-q3rm-f527-ghxj Publify Improper Input Validation vulnerability | Critical | Also affects publify_core |
| GHSA-79wq-g4v9-gfj4 Publify Core does not strip metadata from images | Medium | Also affects publify_core |
| GHSA-wmh9-x28j-c6gr Cross site scripting in publify | Medium | Also affects publify_core |
| GHSA-3h7v-wqw7-ff28 Cross site scripting in publify | Medium | Also affects publify_core |
| GHSA-c273-c6vg-4pv5 Publify has Improper Access Controls | Medium | Also affects publify_core |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor