Skip to content

← Public intelligence

RubyGems package

red-arrow

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.7RubyGemsAmendedPublished

    Missing Initialization of Resource in Apache Arrow

    CVE-2019-12408 · GHSA-8cw2-jv5c-c825

    Affected
    • RubyGems red-arrow >= 0.14.0, < 0.15.1
    Fixed in
    0.15.1· Vendor fix available
    Issue
    It was discovered that the C++ implementation (which underlies the R, Python and Ruby implementations) of Apache Arrow 0.14.0 to 0.14.1 had a uninitialized memory bug when building arrays with null values in some cases. This can lead to uninitialized memory being unintentionally shared if Arrow Arrays are transmitted over the wire (for instance with Flight) or persisted in the streaming IPC and file formats.

    Recommended action: Upgrade to 0.15.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 8.7RubyGemsAmendedPublished

    Missing Initialization of Resource in Apache Arrow

    CVE-2019-12410 · GHSA-cjw4-2w9r-r8mv

    Affected
    • RubyGems red-arrow >= 0.12.0, < 0.15.1
    Fixed in
    0.15.1· Vendor fix available
    Issue
    While investigating UBSAN errors in https://github.com/apache/arrow/pull/5365 it was discovered Apache Arrow versions 0.12.0 to 0.14.1, left memory Array data uninitialized when reading RLE null data from parquet. This affected the C++, Python, Ruby and R implementations. The uninitialized memory could potentially be shared if are transmitted over the wire (for instance with Flight) or persisted in the streaming IPC and file formats.

    Recommended action: Upgrade to 0.15.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →