GHSA-p56p-gq3f-whg8: Flumedb `Read` On Uninitialized Buffer May Vulnerability

HIGH
Share
Published
Advisory Summary

GHSA-p56p-gq3f-whg8 is a HIGH `read` on uninitialized buffer may vulnerability (General Security Weakness) affecting Flumedb libraries in the crates.io ecosystem. The issue involves `read` on uninitialized buffer may cause ub ( `read_entry()` ). Remediation is available by upgrading affected packages to version 0.1.6.

GHSA-p56p-gq3f-whg8 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-p56p-gq3f-whg8
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Flumedb
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-p56p-gq3f-whg8

To remediate this vulnerability, upgrade all affected Flumedb dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

flumedb fixed: 0.1.6 
Upgrade flumedb to 0.1.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for flumedb

How to Check if You Are Affected

To determine whether your application is affected by GHSA-p56p-gq3f-whg8, inspect your project dependencies for Flumedb:

inspect dependencies for flumedb

Analyze the terminal output to locate any version of Flumedb in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.1.6), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Flumedb, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation. There are two of such cases (`go_offset_log::read_entry()` & `offset_log::read_entry()`). 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.

GHSA-p56p-gq3f-whg8 Affected Flumedb Versions

1 component(s)
Fixed Versions:
0.1.6
Product / Package Ecosystem Affected Versions Fixed Version
flumedb
 crates.io
< 0.1.6
0.1.6

References

Flumedb Source Repository REPOSITORY
https://github.com/sunrise-choir/flumedb-rs/issues/10
Flumedb Source Repository REPOSITORY
https://github.com/sunrise-choir/flumedb-rs/pull/12/commits/1b643df85ca4a56f7d96105a9eb35e1b917ee488
Flumedb Source Repository REPOSITORY
https://github.com/sunrise-choir/flumedb-rs
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2021-0086.html

Frequently Asked Questions

What is GHSA-p56p-gq3f-whg8?
GHSA-p56p-gq3f-whg8 is a security vulnerability in Flumedb involving `Read` on uninitialized buffer may cause UB ( `read_entry()` ) under General Security Weakness.
Which Flumedb versions are affected?
Affected versions include releases prior to 0.1.6 across affected packages: flumedb.
What version fixes GHSA-p56p-gq3f-whg8?
Upgrading to 0.1.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is flumedb affected?
Yes, flumedb is affected in releases prior to 0.1.6. Upgrade your dependency to 0.1.6 or later.
What CWE is associated with GHSA-p56p-gq3f-whg8?
GHSA-p56p-gq3f-whg8 is classified under General Security Weakness.
How can I check crates.io dependencies for GHSA-p56p-gq3f-whg8?
Run the dependency tree command: 'inspect dependencies for flumedb'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p56p-gq3f-whg8",
  "modified" : "2022-06-16T23:54:46Z",
  "published" : "2022-06-16T23:54:46Z",
  "aliases" : [ ],
  "summary" : "`Read` on uninitialized buffer may cause UB ( `read_entry()` )",
  "details" : "Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation.\nThere are two of such cases (`go_offset_log::read_entry()` & `offset_log::read_entry()`).\n\nArbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer.\nReading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "flumedb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.1.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/sunrise-choir/flumedb-rs/issues/10"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sunrise-choir/flumedb-rs/pull/12/commits/1b643df85ca4a56f7d96105a9eb35e1b917ee488"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/sunrise-choir/flumedb-rs"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2021-0086.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-06-16T23:54:46Z",
    "nvd_published_at" : null
  }
}