Skip to content

← Public intelligence

crates.io package

flumedb

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. Unratedcrates.ioPublished

    Read on uninitialized buffer may cause UB ( read_entry() )

    GHSA-p56p-gq3f-whg8

    Affected
    • crates.io flumedb < 0.1.6
    Fixed in
    0.1.6· Vendor fix available
    Issue
    Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. There are two of such cases (gooffsetlog::readentry() & offsetlog::readentry()). Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.

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

    Sources:github.comSource checked Evidence →
  2. Critical, CVSS 9.8crates.ioPublished

    Use of Uninitialized Resource in flumedb.

    CVE-2021-45684 · GHSA-p46c-w9m3-7qr2

    Affected
    • crates.io flumedb < 0.1.6
    Fixed in
    0.1.6· Vendor fix available
    Issue
    Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. There are two of such cases (gooffsetlog::readentry() & offsetlog::readentry()). Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.

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

    Sources:github.comSource checked Evidence →