How severe is GHSA-r7cj-wmwv-hfw5?

No CVSS score has been assigned to GHSA-r7cj-wmwv-hfw5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r7cj-wmwv-hfw5?

GHSA-r7cj-wmwv-hfw5 affects the following packages: arrow (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-r7cj-wmwv-hfw5?

Update arrow to 6.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r7cj-wmwv-hfw5 is resolved across your whole dependency graph.

How do I detect GHSA-r7cj-wmwv-hfw5 in my crates.io dependencies?

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

How do I mitigate GHSA-r7cj-wmwv-hfw5 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-r7cj-wmwv-hfw5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r7cj-wmwv-hfw5 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.

When was GHSA-r7cj-wmwv-hfw5 published, and has it been updated?

GHSA-r7cj-wmwv-hfw5 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

`BinaryArray` does not perform bound checks on reading values and offsetsGHSA-r7cj-wmwv-hfw5

GHSA-r7cj-wmwv-hfw5 is a security vulnerability in arrow. A fix is available for arrow — see the affected versions and patch details below.

Also known asRUSTSEC-2021-0116

Published

Jun 16, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀arrow

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

BinaryArray performs insufficient validation on creation, which allows out-of-bounds reads in safe code.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for arrow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update arrow to 6.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r7cj-wmwv-hfw5 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

`BinaryArray` performs insufficient validation on creation, which allows out-of-bounds reads in safe code.

O3 Security · Impact-Aware SCA

Is GHSA-r7cj-wmwv-hfw5 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works