How severe is GHSA-7v4j-8wvr-v55r?

No CVSS score has been assigned to GHSA-7v4j-8wvr-v55r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7v4j-8wvr-v55r?

GHSA-7v4j-8wvr-v55r affects the following packages: array-macro (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-7v4j-8wvr-v55r?

Update array-macro to 2.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7v4j-8wvr-v55r is resolved across your whole dependency graph.

How do I detect GHSA-7v4j-8wvr-v55r in my crates.io dependencies?

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

How do I mitigate GHSA-7v4j-8wvr-v55r 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-7v4j-8wvr-v55r actively exploited in the wild?

No public exploit code has been indexed for GHSA-7v4j-8wvr-v55r 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-7v4j-8wvr-v55r published, and has it been updated?

GHSA-7v4j-8wvr-v55r 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

`array!` macro is unsound when its length is impure constantGHSA-7v4j-8wvr-v55r

Fix: xfix/array-macro@d5b63f7

GHSA-7v4j-8wvr-v55r is a remote code execution vulnerability in array-macro. A fix is available for array-macro — see the affected versions and patch details below.

Also known asRUSTSEC-2022-0017

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

🦀array-macro

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 did substitute the array length provided by an user at compile-time multiple times.

When an impure constant expression is passed as an array length (such as a result of an impure procedural macro), this can result in the initialization of an array with uninitialized types, which in turn can allow an attacker to execute arbitrary code.

The flaw was corrected in commit d5b63f72 by making sure that array length is substituted just once.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`array-macro`	≥ 2.1.0&&< 2.1.2	2.1.2`cargo update -p array-macro --precise 2.1.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for array-macro, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update array-macro to 2.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7v4j-8wvr-v55r 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.

Frequently Asked Questions

Affected versions of this crate did substitute the array length provided by an user at compile-time multiple times. When an impure constant expression is passed as an array length (such as a result of an impure procedural macro), this can result in the initialization of an array with uninitialized types, which in turn can allow an attacker to execute arbitrary code. The flaw was corrected in commit [d5b63f72](https://github.com/xfix/array-macro/commit/d5b63f72090f3809c21ac28f9cfd84f12559bf7d) by making sure that array length is substituted just once.

O3 Security · Impact-Aware SCA

Is GHSA-7v4j-8wvr-v55r in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works