How severe is GHSA-q579-9wp9-gfp2?

No CVSS score has been assigned to GHSA-q579-9wp9-gfp2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q579-9wp9-gfp2?

GHSA-q579-9wp9-gfp2 affects the following packages: rdiff (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-q579-9wp9-gfp2?

The records we use list no patched version of rdiff for GHSA-q579-9wp9-gfp2. 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-q579-9wp9-gfp2 in my crates.io dependencies?

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

How do I mitigate GHSA-q579-9wp9-gfp2 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-q579-9wp9-gfp2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q579-9wp9-gfp2 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-q579-9wp9-gfp2?

GHSA-q579-9wp9-gfp2 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-q579-9wp9-gfp2?

GHSA-q579-9wp9-gfp2 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-q579-9wp9-gfp2 published, and has it been updated?

GHSA-q579-9wp9-gfp2 was published on June 17, 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

Window can read out of bounds if Read instance returns more bytes than buffer sizeGHSA-q579-9wp9-gfp2

GHSA-q579-9wp9-gfp2 is a CWE-908 vulnerability in rdiff. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2021-45694 GHSA-2rxc-8f9w-fjq8RUSTSEC-2021-0094

Published

Jun 17, 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

🦀rdiff

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

rdiff performs a diff of two provided strings or files. As part of its reading code it uses the return value of a Read instance to set the length of its internal character vector.

If the Read implementation claims that it has read more bytes than the length of the provided buffer, the length of the vector will be set to longer than its capacity. This causes rdiff APIs to return uninitialized memory in its API methods.

Affected Packages

1 total

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

Affected Products

1 product · 1 configurations

Application

rdiffrdiff_project

≤ 0.1.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rdiff, 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 rdiff for GHSA-q579-9wp9-gfp2. 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

`rdiff` performs a diff of two provided strings or files. As part of its reading code it uses the return value of a `Read` instance to set the length of its internal character vector. If the `Read` implementation claims that it has read more bytes than the length of the provided buffer, the length of the vector will be set to longer than its capacity. This causes `rdiff` APIs to return uninitialized memory in its API methods.

O3 Security · Impact-Aware SCA

Is GHSA-q579-9wp9-gfp2 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works