LiveActive security incident?Get immediate response
CVE Record

CVE-2019-16892: In Rubyzip before 1.3.0, a crafted ZIP file can bypass application checks on ZIP entry sizes because data a...

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).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Rubyzip before 1.3.0 can be tricked by a ZIP file that lies about how large its contents will be after extraction. Applications that trust that size check may extract much more data than expected, filling disk space and causing a denial of service.

Executive priority

Prioritize systems that process external ZIP files because the business impact is service disruption, not confirmed data compromise. Treat internet-facing upload or ingestion services as the first remediation wave.

Technical view

The issue is an uncompressed-size spoofing problem in Rubyzip before 1.3.0. A crafted archive can bypass application checks based on ZIP entry sizes, leading to disk consumption during processing. The provided sources do not include CVSS, CWE, or evidence of code execution impact.

Likely exposure

Exposure is most likely in Ruby applications or packaged products using rubyzip before 1.3.0, especially services that accept or process user-supplied ZIP archives. Fedora and Red Hat advisories indicate downstream packaged exposure existed.

Exploitation context

The source bundle does not cite active exploitation, and KEV is false. Practical abuse requires a target application to process an attacker-controlled ZIP file and rely on spoofable entry-size metadata for safety checks.

Researcher notes

Evidence is limited to the CVE description, Rubyzip fix references, and Fedora/Red Hat advisories. No CVSS, CWE, or exploitation evidence is provided in the bundle, so impact assessment should remain scoped to denial of service via disk consumption.

Mitigation direction

  • Upgrade rubyzip to 1.3.0 or later where directly bundled.
  • Apply relevant Fedora or Red Hat package updates where rubyzip is OS-managed.
  • Restrict untrusted ZIP uploads until vulnerable dependencies are updated.
  • Enforce disk quotas and extraction limits around archive-processing workloads.
  • Check vendor guidance for affected packaged products before deploying changes.

Validation and detection

  • Search application dependency manifests for rubyzip versions before 1.3.0.
  • Check OS package inventories against the referenced Fedora and Red Hat advisories.
  • Identify public or partner-facing workflows that accept ZIP archives.
  • Confirm archive-processing code does not trust reported uncompressed size alone.
  • Review monitoring for disk exhaustion during archive ingestion paths.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-16892 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.