Read the docs
TI-2022-26570 Aliases GHSA-p56p-gq3f-whg8

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

Priority LOW 38Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub.

Summary

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.

Why it matters now

Fix Fixed flumedb (crates.io): 0.1.6

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—flumedb (crates.io)before 0.1.60.1.6Patch availableGHSA-p56p-gq3f-whg8
  • flumedb (crates.io) Vendor— Affected before 0.1.6 Fixed in 0.1.6 Patch available GHSA-p56p-gq3f-whg8

Remediation

  • Fix · GHSA-p56p-gq3f-whg8 flumedb (crates.io) Fixed in 0.1.6 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-p56p-gq3f-whg8

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences