How severe is GHSA-72r2-rg28-47v9?

No CVSS score has been assigned to GHSA-72r2-rg28-47v9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-72r2-rg28-47v9?

GHSA-72r2-rg28-47v9 affects the following packages: bite (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-72r2-rg28-47v9?

The records we use list no patched version of bite for GHSA-72r2-rg28-47v9. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-72r2-rg28-47v9 in my crates.io dependencies?

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

How do I mitigate GHSA-72r2-rg28-47v9 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-72r2-rg28-47v9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-72r2-rg28-47v9 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-72r2-rg28-47v9?

GHSA-72r2-rg28-47v9 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 66th 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-72r2-rg28-47v9?

GHSA-72r2-rg28-47v9 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-72r2-rg28-47v9 published, and has it been updated?

GHSA-72r2-rg28-47v9 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 (bite::read::BiteReadExpandedExt::read_framed_max)GHSA-72r2-rg28-47v9

GHSA-72r2-rg28-47v9 is a CWE-908 vulnerability in bite. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2020-36511 GHSA-v2ch-fc8f-qm33RUSTSEC-2020-0153

Published

Jun 16, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🦀bite

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 calls a user provided Read implementation on an uninitialized buffer. Read on uninitialized buffer is defined as undefined behavior in Rust.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`bite`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

bitebite_project

≤ 0.0.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 bite, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of bite for GHSA-72r2-rg28-47v9. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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 calls a user provided `Read` implementation on an uninitialized buffer. `Read` on uninitialized buffer is defined as undefined behavior in Rust.

O3 Security · Impact-Aware SCA

Is GHSA-72r2-rg28-47v9 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works