How severe is GHSA-5j8w-r7g8-5472?

No CVSS score has been assigned to GHSA-5j8w-r7g8-5472 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5j8w-r7g8-5472?

GHSA-5j8w-r7g8-5472 affects the following packages: arrow2 (crates.io), arrow2 (crates.io), arrow2 (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-5j8w-r7g8-5472?

Update arrow2 to 0.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5j8w-r7g8-5472 is resolved across your whole dependency graph.

How do I detect GHSA-5j8w-r7g8-5472 in my crates.io dependencies?

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

How do I mitigate GHSA-5j8w-r7g8-5472 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-5j8w-r7g8-5472?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5j8w-r7g8-5472 can be triaged on real exposure rather than presence alone.

Is GHSA-5j8w-r7g8-5472 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5j8w-r7g8-5472 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-5j8w-r7g8-5472 published, and has it been updated?

GHSA-5j8w-r7g8-5472 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

GHSA-5j8w-r7g8-5472 — arrow2

GHSA-5j8w-r7g8-5472 is a security vulnerability in arrow2. A fix is available for arrow2 — see the affected versions and patch details below.

Arrow2 allows double free in `safe` code

Also known asRUSTSEC-2022-0012

Published

Jun 16, 2022

Updated

Nov 8, 2023

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Real-World Exposure

3 pkgs affected

🦀arrow2🦀arrow2🦀arrow2

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

The struct Ffi_ArrowArray implements #derive(Clone) that is inconsistent with its custom implementation of Drop, resulting in a double free when cloned.

Cloning this struct in safe results in a segmentation fault, which is unsound.

This derive was removed from this struct. All users are advised to either:

bump the patch version of this crate (for versions v0.7,v0.8,v0.9), or
migrate to a more recent version of the crate (when using <0.7).

Doing so elimitates this vulnerability (code no longer compiles).

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`arrow2`	all versions	0.7.1`cargo update -p arrow2 --precise 0.7.1`
🦀crates.io	`arrow2`	≥ 0.8.0&&< 0.8.2	0.8.2`cargo update -p arrow2 --precise 0.8.2`
🦀crates.io	`arrow2`	≥ 0.9.0&&< 0.9.2	0.9.2`cargo update -p arrow2 --precise 0.9.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for arrow2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update arrow2 to 0.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5j8w-r7g8-5472 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5j8w-r7g8-5472 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-5j8w-r7g8-5472. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The struct `Ffi_ArrowArray` implements `#derive(Clone)` that is inconsistent with its custom implementation of `Drop`, resulting in a double free when cloned. Cloning this struct in `safe` results in a segmentation fault, which is unsound. This derive was removed from this struct. All users are advised to either: * bump the patch version of this crate (for versions `v0.7,v0.8,v0.9`), or * migrate to a more recent version of the crate (when using `<0.7`). Doing so elimitates this vulnerability (code no longer compiles).

O3 Security · Impact-Aware SCA

Is GHSA-5j8w-r7g8-5472 in your dependencies?

O3 Security finds GHSA-5j8w-r7g8-5472 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works