How severe is GHSA-r67p-m7g9-gxw6?

No CVSS score has been assigned to GHSA-r67p-m7g9-gxw6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r67p-m7g9-gxw6?

GHSA-r67p-m7g9-gxw6 affects the following packages: csv-sniffer (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-r67p-m7g9-gxw6?

Update csv-sniffer to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r67p-m7g9-gxw6 is resolved across your whole dependency graph.

How do I detect GHSA-r67p-m7g9-gxw6 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for csv-sniffer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-r67p-m7g9-gxw6 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.

How does O3 Security protect against GHSA-r67p-m7g9-gxw6?

O3 pinpoints whether GHSA-r67p-m7g9-gxw6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-r67p-m7g9-gxw6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r67p-m7g9-gxw6 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 type of vulnerability is GHSA-r67p-m7g9-gxw6?

GHSA-r67p-m7g9-gxw6 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-r67p-m7g9-gxw6 published, and has it been updated?

GHSA-r67p-m7g9-gxw6 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

GHSA-r67p-m7g9-gxw6

GHSA-r67p-m7g9-gxw6 is a CWE-908 vulnerability in csv-sniffer. O3 Security confirms whether GHSA-r67p-m7g9-gxw6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

`Read` on uninitialized memory may cause UB (fn preamble_skipcount())

Also known asCVE-2021-45686 GHSA-9783-42pm-x5jqRUSTSEC-2021-0088

Published

Jun 16, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🦀csv-sniffer

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 (within fn preamble_skipcount()).

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	`csv-sniffer`	all versions	0.2.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for csv-sniffer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update csv-sniffer to 0.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r67p-m7g9-gxw6 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.
How O3 protects you
O3 pinpoints whether GHSA-r67p-m7g9-gxw6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-r67p-m7g9-gxw6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation (within `fn preamble_skipcount()`). 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.

O3 Security · Impact-Aware SCA

Is GHSA-r67p-m7g9-gxw6 in your dependencies?

O3 detects GHSA-r67p-m7g9-gxw6 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works