Skip to content

GHSA-5m2v-hc64-56h6 CVE-2019-16892

Rubyzip denial of service

Medium RubyGems
Severity
5.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
1.58%
Chance of exploitation in the next 30 days. Higher than 75.53% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-400 Uncontrolled Resource Consumption
Fix
1.3.0
Upgrade rubyzip to this version or later

Description

In Rubyzip before 1.3.0, a crafted ZIP file can bypass application checks on ZIP entry sizes because data about the uncompressed size can be spoofed. This allows attackers to cause a denial of service (disk consumption).

Affected versions

RubyGems

PackageVulnerableFixed in
rubyzip
< 1.3.0
1.3.0

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.

rubyzip RubyGems → 1.3.0

bundler
bundle update rubyzip # Gemfile: gem "rubyzip", ">= 1.3.0"

Severity breakdown

CVSS 3.1 5.5

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
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

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-47m2-wp7j-p9vc
rubyzip path traversal vulnerability
High Also affects rubyzip
GHSA-vqcq-mrmw-mcmg
Rubyzip gem contains a Directory Traversal vulnerability in zip file component
Critical Also affects rubyzip
GHSA-gcqq-w6gr-h9j9
Directory traversal vulnerability in RubyZip
Critical Also affects rubyzip
GHSA-cggf-277g-3q54
pypdf has possible large memory usage when parsing page tree
High Same weakness, CWE-400
GHSA-3g3m-2fjr-6pw4
Glob: AbortSignal cancellation bypass allows post-timeout filesystem traversal
Medium Same weakness, CWE-400
GHSA-42gh-23hr-vphw
pypdf has possible long runtimes when retrieving page labels
High Same weakness, CWE-400
GHSA-4vqv-7265-gm2w
pypdf has possible large memory usage for exceptions in strict mode
High Same weakness, CWE-400
GHSA-62m5-6wh8-28x7
pypdf has possible long runtimes/large memory usage for encrypted PDF files
High Same weakness, CWE-400
Is this in your code?

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