How severe is GHSA-p56p-gq3f-whg8?

No CVSS score has been assigned to GHSA-p56p-gq3f-whg8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p56p-gq3f-whg8?

GHSA-p56p-gq3f-whg8 affects the following packages: flumedb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-p56p-gq3f-whg8?

Update flumedb to 0.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p56p-gq3f-whg8 is resolved across your whole dependency graph.

How do I detect GHSA-p56p-gq3f-whg8 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flumedb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-p56p-gq3f-whg8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-p56p-gq3f-whg8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p56p-gq3f-whg8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-p56p-gq3f-whg8?

GHSA-p56p-gq3f-whg8 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-p56p-gq3f-whg8?

GHSA-p56p-gq3f-whg8 is classified as CWE-908 (CWE-908). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-p56p-gq3f-whg8 published, and has it been updated?

GHSA-p56p-gq3f-whg8 was published on June 16, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

`Read` on uninitialized buffer may cause UB ( `read_entry()` )GHSA-p56p-gq3f-whg8

Fix: sunrise-choir/flumedb-rs#12

GHSA-p56p-gq3f-whg8 is a CWE-908 vulnerability in flumedb. A fix is available for flumedb — see the affected versions and patch details below.

Also known asCVE-2021-45684 GHSA-p46c-w9m3-7qr2RUSTSEC-2021-0086

Published

Jun 16, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🦀flumedb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`flumedb`	all versions	0.1.6`cargo update -p flumedb --precise 0.1.6`

Affected Products

1 product · 1 configurations

Application

flumedbflumedb_project

≤ 0.1.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flumedb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update flumedb to 0.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p56p-gq3f-whg8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.